Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf9d346ac8cc587c4a95625ea858fa06da9b2d857443211d66337f8491a3ac39

Tx prefix hash: 6630d950e106e46137b6800c63f49c7481b2bb5d2340656601dec3b772299a0d
Tx public key: 9cbe7bb4b192d54d70b97cb1b0592370b9ba7be0ec86d9fb76a8fc48ba65af53
Timestamp: 1732417317 Timestamp [UCT]: 2024-11-24 03:01:57 Age [y:d:h:m:s]: 00:125:11:17:48
Block: 1160406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89478 RingCT/type: yes/0
Extra: 019cbe7bb4b192d54d70b97cb1b0592370b9ba7be0ec86d9fb76a8fc48ba65af53021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 689fd330de35d328260ee0d004c5956255b6a20c899761dc5fbfc77c877a1be1 0.600000000000 1646053 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": 1160416, "vin": [ { "gen": { "height": 1160406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "689fd330de35d328260ee0d004c5956255b6a20c899761dc5fbfc77c877a1be1" } } ], "extra": [ 1, 156, 190, 123, 180, 177, 146, 213, 77, 112, 185, 124, 177, 176, 89, 35, 112, 185, 186, 123, 224, 236, 134, 217, 251, 118, 168, 252, 72, 186, 101, 175, 83, 2, 17, 0, 0, 0, 4, 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