Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d6a9c3ab19ea95d0f0cf00f2d8a56a078c6e0379d85fe1a87ad6ea77523a064

Tx prefix hash: 6803f4526b3d3cbf7fa864729f2b6740dd378a2c942d5a8c07bb152194ea796b
Tx public key: 7221ffcb829142411b37ac9576f830bc134dc5e8bbee5e4f1cefec470386390a
Timestamp: 1709667663 Timestamp [UCT]: 2024-03-05 19:41:03 Age [y:d:h:m:s]: 00:357:15:25:16
Block: 971907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255697 RingCT/type: yes/0
Extra: 017221ffcb829142411b37ac9576f830bc134dc5e8bbee5e4f1cefec470386390a0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bf2bf72de46f5fbb2c6c75875f5b9484fc6411ce13a284fd76221855116d766 0.600000000000 1431812 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": 971917, "vin": [ { "gen": { "height": 971907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bf2bf72de46f5fbb2c6c75875f5b9484fc6411ce13a284fd76221855116d766" } } ], "extra": [ 1, 114, 33, 255, 203, 130, 145, 66, 65, 27, 55, 172, 149, 118, 248, 48, 188, 19, 77, 197, 232, 187, 238, 94, 79, 28, 239, 236, 71, 3, 134, 57, 10, 2, 17, 0, 0, 0, 3, 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