Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2caa4561d0432411638fe8bf912e5b6ac8f96f6d2454ee3e5a90256c211be47f

Tx prefix hash: 0bebc0c960854d5c97474ec8e1d7002858c7793f7b680dd333c66b7031ad4eb6
Tx public key: 427e67b05d2f163ae51e0914cf195b3eb2a8413be226f2fee45f8dd3d9585985
Timestamp: 1722896444 Timestamp [UCT]: 2024-08-05 22:20:44 Age [y:d:h:m:s]: 00:274:11:15:36
Block: 1081571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196069 RingCT/type: yes/0
Extra: 01427e67b05d2f163ae51e0914cf195b3eb2a8413be226f2fee45f8dd3d958598502110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1fc7f16b94a857ab9c7bfd331b9e30be133bc144093c4fa637d11873c7c9682 0.600000000000 1555368 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": 1081581, "vin": [ { "gen": { "height": 1081571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1fc7f16b94a857ab9c7bfd331b9e30be133bc144093c4fa637d11873c7c9682" } } ], "extra": [ 1, 66, 126, 103, 176, 93, 47, 22, 58, 229, 30, 9, 20, 207, 25, 91, 62, 178, 168, 65, 59, 226, 38, 242, 254, 228, 95, 141, 211, 217, 88, 89, 133, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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