Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b3570310094608224f62742bde4a8891aff069502fcaa2e0f6d7ff2de586623

Tx prefix hash: 4159a947e3d748dc21d9c10e4aad9d9b1f28d6635d445101988b2bae367b9fa7
Tx public key: 8a8453fa41821168e8a488bbfef222e451ed472a5d5ecefa1a7a057410ad5d70
Timestamp: 1720207403 Timestamp [UCT]: 2024-07-05 19:23:23 Age [y:d:h:m:s]: 00:314:17:03:38
Block: 1059270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224894 RingCT/type: yes/0
Extra: 018a8453fa41821168e8a488bbfef222e451ed472a5d5ecefa1a7a057410ad5d700211000000038fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ffd73f481ea39f981a16e9e54d8ec4e4058fa026e39d2934d42dccb376d8171 0.600000000000 1529737 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": 1059280, "vin": [ { "gen": { "height": 1059270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ffd73f481ea39f981a16e9e54d8ec4e4058fa026e39d2934d42dccb376d8171" } } ], "extra": [ 1, 138, 132, 83, 250, 65, 130, 17, 104, 232, 164, 136, 187, 254, 242, 34, 228, 81, 237, 71, 42, 93, 94, 206, 250, 26, 122, 5, 116, 16, 173, 93, 112, 2, 17, 0, 0, 0, 3, 143, 218, 155, 45, 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