Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d521dc33761a9d5a15b7356113f9b28e1ebb133b791ea15963c410f76fcf73df

Tx prefix hash: 3886d0a0e02992b95652183a825578dc346dc45623b4c54b5b01d032055dab25
Tx public key: 9ab848e7d0076b4ab4fbf55da2c90a1612ca01287feae06079fdb3a2be312571
Timestamp: 1751164106 Timestamp [UCT]: 2025-06-29 02:28:26 Age [y:d:h:m:s]: 00:144:19:32:42
Block: 1314926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101592 RingCT/type: yes/0
Extra: 019ab848e7d0076b4ab4fbf55da2c90a1612ca01287feae06079fdb3a2be312571021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acf0c3201b8d2a424caced28d2a4d55f70296899a13b2ee6bd12679037c007b8 0.600000000000 1802579 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": 1314936, "vin": [ { "gen": { "height": 1314926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acf0c3201b8d2a424caced28d2a4d55f70296899a13b2ee6bd12679037c007b8" } } ], "extra": [ 1, 154, 184, 72, 231, 208, 7, 107, 74, 180, 251, 245, 93, 162, 201, 10, 22, 18, 202, 1, 40, 127, 234, 224, 96, 121, 253, 179, 162, 190, 49, 37, 113, 2, 17, 0, 0, 0, 1, 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