Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96ac4e0fe46c722684e6f6636926fd44dc69ad1cab5511cc6867b406fa65a4bf

Tx prefix hash: e35dd46f28977bc9aeafb69e0015e6ac9bdcb79bf2b6c9a17ae2f77de29856e4
Tx public key: 2fd904718424d2abcd4f5e5c92f1c28e9186ff6728cc6247fab2d98c77717d3c
Timestamp: 1734197483 Timestamp [UCT]: 2024-12-14 17:31:23 Age [y:d:h:m:s]: 00:103:20:50:51
Block: 1175168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74004 RingCT/type: yes/0
Extra: 012fd904718424d2abcd4f5e5c92f1c28e9186ff6728cc6247fab2d98c77717d3c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8adfe83a77e21005c8a76b1925062463796c231056ca62f0692c9c795ed5f019 0.600000000000 1661409 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": 1175178, "vin": [ { "gen": { "height": 1175168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8adfe83a77e21005c8a76b1925062463796c231056ca62f0692c9c795ed5f019" } } ], "extra": [ 1, 47, 217, 4, 113, 132, 36, 210, 171, 205, 79, 94, 92, 146, 241, 194, 142, 145, 134, 255, 103, 40, 204, 98, 71, 250, 178, 217, 140, 119, 113, 125, 60, 2, 17, 0, 0, 0, 3, 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