Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc4b74f2a245f7f16c00914acf7a4c03591e6816095e6d20d6d0fac278b305e6

Tx prefix hash: cfffaf20d0839f86152c6c9f7c81ba3b28317b18d0f851da17529ae0f25538e7
Tx public key: ea00fd5f5fd7fe5dda0dc1c2a5bc3c12de198549cf98dbf2a2805ba3361b667e
Timestamp: 1708934693 Timestamp [UCT]: 2024-02-26 08:04:53 Age [y:d:h:m:s]: 01:032:00:56:23
Block: 965825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283906 RingCT/type: yes/0
Extra: 01ea00fd5f5fd7fe5dda0dc1c2a5bc3c12de198549cf98dbf2a2805ba3361b667e0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1651d9a70c56cda6a868359f8c89f1d3d3f188676a8e70325235447edb79e7cd 0.600000000000 1425580 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": 965835, "vin": [ { "gen": { "height": 965825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1651d9a70c56cda6a868359f8c89f1d3d3f188676a8e70325235447edb79e7cd" } } ], "extra": [ 1, 234, 0, 253, 95, 95, 215, 254, 93, 218, 13, 193, 194, 165, 188, 60, 18, 222, 25, 133, 73, 207, 152, 219, 242, 162, 128, 91, 163, 54, 27, 102, 126, 2, 17, 0, 0, 0, 7, 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