Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: be9793285a75482d6b8bf84b0d5cc3cdb2f295546fe5f7dd91aff8cd29fc6f9f

Tx prefix hash: d3f52cb3d8666a5d5b30238ae4aef84121ee78c9501d99d18f4d84d88703da18
Tx public key: 608d02f10efcbcd72b415a7a1d1ce326399311cb10d5308f70752d619e3269b4
Timestamp: 1583860471 Timestamp [UTC]: 2020-03-10 17:14:31 Age [y:d:h:m:s]: 05:355:18:06:28
Block: 80090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1407502 RingCT/type: yes/0
Extra: 01608d02f10efcbcd72b415a7a1d1ce326399311cb10d5308f70752d619e3269b40211000000014ac5aa02000000000000000000

1 output(s) for total of 0.333141987879 xmr

stealth address amount amount idx tag
00: 50c321ba5bf0795f3fb4c3546dbb07cce91cc5f68975d6dbf2e18d3ce816ae4c 0.333141987879 146546 of 0 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 80100, "vin": [ { "gen": { "height": 80090 } } ], "vout": [ { "amount": 333141987879, "target": { "key": "50c321ba5bf0795f3fb4c3546dbb07cce91cc5f68975d6dbf2e18d3ce816ae4c" } } ], "extra": [ 1, 96, 141, 2, 241, 14, 252, 188, 215, 43, 65, 90, 122, 29, 28, 227, 38, 57, 147, 17, 203, 16, 213, 48, 143, 112, 117, 45, 97, 158, 50, 105, 180, 2, 17, 0, 0, 0, 1, 74, 197, 170, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369