Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9d2d4501272484872e686a266ee6bfc07d3ff031ad9eba9c6ee25469991def2

Tx prefix hash: ddc6d42ae534d4bd9f822e91320f1f7244cc0185dc20685b2c50ed937df66410
Tx public key: d57d55ccfbf7afe9e7cdd766e647af8b017ed1f68d40944086f4252d5aa38026
Timestamp: 1760989132 Timestamp [UTC]: 2025-10-20 19:38:52 Age [y:d:h:m:s]: 01:031:17:47:57
Block: 1394281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289150 RingCT/type: yes/0
Extra: 01d57d55ccfbf7afe9e7cdd766e647af8b017ed1f68d40944086f4252d5aa3802602110000000501491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5d49556ff53c8b504bf84ad32217cc94e83be748bd01e6466e31c4a65bea6093 0.000600000000 1882552 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": 1394291, "vin": [ { "gen": { "height": 1394281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d49556ff53c8b504bf84ad32217cc94e83be748bd01e6466e31c4a65bea6093" } } ], "extra": [ 1, 213, 125, 85, 204, 251, 247, 175, 233, 231, 205, 215, 102, 230, 71, 175, 139, 1, 126, 209, 246, 141, 64, 148, 64, 134, 244, 37, 45, 90, 163, 128, 38, 2, 17, 0, 0, 0, 5, 1, 73, 31, 136, 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: