Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3e7965256821f6b39db83d61fc625c57db1d88951221d13988aca17c74c7452

Tx prefix hash: 3c883437311b15d4e4fd618ba44ae55d0019999c97ad2f06950c9607f2d26009
Tx public key: c602b012441a18b2dabf07e4af1a2c27e52965631f59d31ac1ac06d5c0cfc6be
Timestamp: 1716500557 Timestamp [UCT]: 2024-05-23 21:42:37 Age [y:d:h:m:s]: 00:184:13:03:44
Block: 1028550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132080 RingCT/type: yes/0
Extra: 01c602b012441a18b2dabf07e4af1a2c27e52965631f59d31ac1ac06d5c0cfc6be0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f701f47f3d478e9644e8ae6bec30c8e5895dd05d3d5dd3e4db65a7142b008dbf 0.600000000000 1496543 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": 1028560, "vin": [ { "gen": { "height": 1028550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f701f47f3d478e9644e8ae6bec30c8e5895dd05d3d5dd3e4db65a7142b008dbf" } } ], "extra": [ 1, 198, 2, 176, 18, 68, 26, 24, 178, 218, 191, 7, 228, 175, 26, 44, 39, 229, 41, 101, 99, 31, 89, 211, 26, 193, 172, 6, 213, 192, 207, 198, 190, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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