Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d02439ba5bc345db353ca6d0d47ba319c0e393e1cc23d06e2a340e283c887ec

Tx prefix hash: 9338c39d671d2a105cf9258fec15aa9417c7419aca0d8cfe2714e4ec3314ccf8
Tx public key: 378a00b267de0ad9a4e0cfdf591b688892623696ced235e224c53dbe56d6a623
Timestamp: 1756706030 Timestamp [UTC]: 2025-09-01 05:53:50 Age [y:d:h:m:s]: 01:080:01:59:33
Block: 1358883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323643 RingCT/type: yes/0
Extra: 01378a00b267de0ad9a4e0cfdf591b688892623696ced235e224c53dbe56d6a623021100000003b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c87016406dd72d77ec7d4fd5fac25bbb1b66843ca93d6301b8945a19fc3a62f7 0.000600000000 1846896 of 15 -

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": 1358893, "vin": [ { "gen": { "height": 1358883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c87016406dd72d77ec7d4fd5fac25bbb1b66843ca93d6301b8945a19fc3a62f7" } } ], "extra": [ 1, 55, 138, 0, 178, 103, 222, 10, 217, 164, 224, 207, 223, 89, 27, 104, 136, 146, 98, 54, 150, 206, 210, 53, 226, 36, 197, 61, 190, 86, 214, 166, 35, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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) | monero version: