Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 997e96b27c85bd58305b6b7e86ce0c2db8a4b8459c2faed0211a7fde57231493

Tx prefix hash: 8b76de3c946aa200d869e894fb584665278c5ca1efd03483dd1ff8324ca09a04
Tx public key: 83a9879270407f17930baad2c17044b3ba66f28e6452e73fef87ec443e7150b5
Timestamp: 1772299800 Timestamp [UTC]: 2026-02-28 17:30:00 Age [y:d:h:m:s]: 00:262:19:56:23
Block: 1487779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193381 RingCT/type: yes/0
Extra: 0183a9879270407f17930baad2c17044b3ba66f28e6452e73fef87ec443e7150b5021100000008e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ab6f2a922b419b95d8f269bcf0b96d64d68f07dd508c412a8d38fb111caaa55c 0.000600000000 1977251 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": 1487789, "vin": [ { "gen": { "height": 1487779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab6f2a922b419b95d8f269bcf0b96d64d68f07dd508c412a8d38fb111caaa55c" } } ], "extra": [ 1, 131, 169, 135, 146, 112, 64, 127, 23, 147, 11, 170, 210, 193, 112, 68, 179, 186, 102, 242, 142, 100, 82, 231, 63, 239, 135, 236, 68, 62, 113, 80, 181, 2, 17, 0, 0, 0, 8, 228, 245, 25, 63, 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: