Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 900e319ed9e31762391c543e28e775cbeeb8cc442d331ecb03e0e36729c73835

Tx prefix hash: 3f3c9992a72590a612b7fa27d6f5be5135ed30668a34b813c80b907410571dd5
Tx public key: d2cd0495ce95cbe59de8c7610b37aa94e700f3cd43610d94a5c1bb3c748c0d3f
Timestamp: 1750190523 Timestamp [UCT]: 2025-06-17 20:02:03 Age [y:d:h:m:s]: 00:151:21:31:00
Block: 1307171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106354 RingCT/type: yes/0
Extra: 01d2cd0495ce95cbe59de8c7610b37aa94e700f3cd43610d94a5c1bb3c748c0d3f021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36edd7decbeca43f19e1d2ff06cbcd92f5c8d40932cc1cc437fa12f68f16226f 0.600000000000 1794780 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 dinasty-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": 1307181, "vin": [ { "gen": { "height": 1307171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36edd7decbeca43f19e1d2ff06cbcd92f5c8d40932cc1cc437fa12f68f16226f" } } ], "extra": [ 1, 210, 205, 4, 149, 206, 149, 203, 229, 157, 232, 199, 97, 11, 55, 170, 148, 231, 0, 243, 205, 67, 97, 13, 148, 165, 193, 187, 60, 116, 140, 13, 63, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8