Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db0dcfe57f4d89c62a24196720eb7c4276469eda72d437b178026a58076b3747

Tx prefix hash: 8176c3cdbecfcdf7cbcc5acec459809c4d64012b333522f39ed706bd71a3e6c5
Tx public key: 1af185721d5c4096ad6fc6dd315f8b3951e38c085fcee66a568e2c3c997fd1fd
Timestamp: 1736787396 Timestamp [UCT]: 2025-01-13 16:56:36 Age [y:d:h:m:s]: 00:156:15:57:58
Block: 1196594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111648 RingCT/type: yes/0
Extra: 011af185721d5c4096ad6fc6dd315f8b3951e38c085fcee66a568e2c3c997fd1fd02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4eda245f82165ccc5d6d7a1143556275efefa634e631d818c890886e4a684324 0.600000000000 1683193 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": 1196604, "vin": [ { "gen": { "height": 1196594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4eda245f82165ccc5d6d7a1143556275efefa634e631d818c890886e4a684324" } } ], "extra": [ 1, 26, 241, 133, 114, 29, 92, 64, 150, 173, 111, 198, 221, 49, 95, 139, 57, 81, 227, 140, 8, 95, 206, 230, 106, 86, 142, 44, 60, 153, 127, 209, 253, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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