Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 010cf2a2cad151c4bff04453da2c99a4fd1d06abf23e44dfa64820627020d696

Tx prefix hash: 20055fe1065f52151a66d8fc8b1b0462f750a2599866ab256d54365486d1fb69
Tx public key: e9ac3bb68a4bce5a18005c5c2f577be1130665e607961519a7834a9a10f6570c
Timestamp: 1771172838 Timestamp [UTC]: 2026-02-15 16:27:18 Age [y:d:h:m:s]: 00:109:10:59:51
Block: 1478448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73135 RingCT/type: yes/0
Extra: 01e9ac3bb68a4bce5a18005c5c2f577be1130665e607961519a7834a9a10f6570c021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 593ad9c510ae63552389419d28fdd7723ef34ae01d3a41d4764d2d81fcd5dddc 0.000600000000 1967778 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": 1478458, "vin": [ { "gen": { "height": 1478448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "593ad9c510ae63552389419d28fdd7723ef34ae01d3a41d4764d2d81fcd5dddc" } } ], "extra": [ 1, 233, 172, 59, 182, 138, 75, 206, 90, 24, 0, 92, 92, 47, 87, 123, 225, 19, 6, 101, 230, 7, 150, 21, 25, 167, 131, 74, 154, 16, 246, 87, 12, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: