Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d449e638bade30cbf425da4a1a845bc906b73ce5a2d6ab9863e1423db12b3eb

Tx prefix hash: 7b852d897d0f94c1dfea49383465721089cb8e6d0c2aaf889b54116a0d2d046a
Tx public key: c04edd04f5f8e8464b93e1e083c2a35b0c9b5f3ff7eafdedeccbdc8794d0b30b
Timestamp: 1709396438 Timestamp [UCT]: 2024-03-02 16:20:38 Age [y:d:h:m:s]: 00:328:08:33:59
Block: 969654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235006 RingCT/type: yes/0
Extra: 01c04edd04f5f8e8464b93e1e083c2a35b0c9b5f3ff7eafdedeccbdc8794d0b30b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0b770046b8094778de7f85985da7719cec9f6ad8edd487993e4134064936493 0.600000000000 1429491 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": 969664, "vin": [ { "gen": { "height": 969654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0b770046b8094778de7f85985da7719cec9f6ad8edd487993e4134064936493" } } ], "extra": [ 1, 192, 78, 221, 4, 245, 248, 232, 70, 75, 147, 225, 224, 131, 194, 163, 91, 12, 155, 95, 63, 247, 234, 253, 237, 236, 203, 220, 135, 148, 208, 179, 11, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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