Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed72ca3ba92c9009725e2245911c8ef01fdc263811de9a10f595e8691190313f

Tx prefix hash: ba220d3ea4ee8dbbc60444717c76ef1fea29cc3c3acaa79a6fd57aadf50916a4
Tx public key: 9e2f91546b6774aa687faabcaae240e5d0b0286d3870b6bb4d89d7881fb38a22
Timestamp: 1734882589 Timestamp [UCT]: 2024-12-22 15:49:49 Age [y:d:h:m:s]: 00:101:11:46:07
Block: 1180852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72280 RingCT/type: yes/0
Extra: 019e2f91546b6774aa687faabcaae240e5d0b0286d3870b6bb4d89d7881fb38a22021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe8415b3d28ae61a57eed5d4d75a8e53dc4b7ee5973d38fb88d31d6c6cc899cd 0.600000000000 1667267 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": 1180862, "vin": [ { "gen": { "height": 1180852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe8415b3d28ae61a57eed5d4d75a8e53dc4b7ee5973d38fb88d31d6c6cc899cd" } } ], "extra": [ 1, 158, 47, 145, 84, 107, 103, 116, 170, 104, 127, 170, 188, 170, 226, 64, 229, 208, 176, 40, 109, 56, 112, 182, 187, 77, 137, 215, 136, 31, 179, 138, 34, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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