Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69d2ff424793db8ffefbd8c6c0eed890d30d94c0593d1a94a5a917c54b6f4ed9

Tx prefix hash: 99b31908db1b68723a700fd2e5b0dd7030bf69f1c9acbc8594822e4d42903b08
Tx public key: 7a724469231fa0e84456c049fedd81a73e30e01909feacf103d0e69c5ae7a6e1
Timestamp: 1784108289 Timestamp [UTC]: 2026-07-15 09:38:09 Age [y:d:h:m:s]: 00:130:07:48:56
Block: 1582811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 100683 RingCT/type: yes/0
Extra: 017a724469231fa0e84456c049fedd81a73e30e01909feacf103d0e69c5ae7a6e10208ac2e7f811a34cfb1

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bc98c21437c6999047e594c411a685a15e2bf9f34b0ee309b2e1af1ec37032a2 0.000600000000 2072805 of 15 <17>

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": 1582821, "vin": [ { "gen": { "height": 1582811 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "bc98c21437c6999047e594c411a685a15e2bf9f34b0ee309b2e1af1ec37032a2", "view_tag": "17" } } } ], "extra": [ 1, 122, 114, 68, 105, 35, 31, 160, 232, 68, 86, 192, 73, 254, 221, 129, 167, 62, 48, 224, 25, 9, 254, 172, 241, 3, 208, 230, 156, 90, 231, 166, 225, 2, 8, 172, 46, 127, 129, 26, 52, 207, 177 ], "rct_signatures": { "type": 0 } }


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