Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 735dc996e6088084bbd226a9029a0dc15527ec6ab5f3f636986448c25a414852

Tx prefix hash: 8af4eb99d4b951a59b3831c7c021812cfe0f77b60954f45f87efec4017986a98
Tx public key: 4f0448075f8300f9dc1fd35a33f85b5fbe2ecaa541c55d82bcf62521a0d87b07
Timestamp: 1752867430 Timestamp [UCT]: 2025-07-18 19:37:10 Age [y:d:h:m:s]: 00:197:16:36:14
Block: 1328325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139988 RingCT/type: yes/0
Extra: 014f0448075f8300f9dc1fd35a33f85b5fbe2ecaa541c55d82bcf62521a0d87b0702110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d80f8b7ae0da567cbe6665094eb7ec3ad1838955cc28d0f003d21c31008a5bbc 0.600000000000 1816086 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": 1328335, "vin": [ { "gen": { "height": 1328325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d80f8b7ae0da567cbe6665094eb7ec3ad1838955cc28d0f003d21c31008a5bbc" } } ], "extra": [ 1, 79, 4, 72, 7, 95, 131, 0, 249, 220, 31, 211, 90, 51, 248, 91, 95, 190, 46, 202, 165, 65, 197, 93, 130, 188, 246, 37, 33, 160, 216, 123, 7, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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