Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd15480501fb659a87c2c31630a2d8a97554dc44f575e6648ca04a3514af7e48

Tx prefix hash: ef1d46aa0266b86d4a5be2d56d89799c47dfe4167954bdea5243f18daf02ec96
Tx public key: d0f1167cde2492e14daa34aa1ce11974587fdb1ccc708c0895a1e103133dc47d
Timestamp: 1768959484 Timestamp [UTC]: 2026-01-21 01:38:04 Age [y:d:h:m:s]: 00:305:10:30:48
Block: 1460164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223330 RingCT/type: yes/0
Extra: 01d0f1167cde2492e14daa34aa1ce11974587fdb1ccc708c0895a1e103133dc47d02110000000349d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 51c88324e6b93efdfd47b06b5a53db6771d3c0e4f6c94cf55d82225007332859 0.000600000000 1949332 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": 1460174, "vin": [ { "gen": { "height": 1460164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51c88324e6b93efdfd47b06b5a53db6771d3c0e4f6c94cf55d82225007332859" } } ], "extra": [ 1, 208, 241, 22, 124, 222, 36, 146, 225, 77, 170, 52, 170, 28, 225, 25, 116, 88, 127, 219, 28, 204, 112, 140, 8, 149, 161, 225, 3, 19, 61, 196, 125, 2, 17, 0, 0, 0, 3, 73, 215, 62, 152, 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: