Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f40d450936981c8fb55cedec12887bab81a5e6e5777bb30c761bd44d2b90f809

Tx prefix hash: 180df37a313ef484baa4de984a3a51ca918390da167d0ca4a135ce044f6f079f
Tx public key: 66d5b7aeecd9ba8a9dd0c6cac14ef518788f0f838c78454eafc0bbfc595772f5
Timestamp: 1724220712 Timestamp [UCT]: 2024-08-21 06:11:52 Age [y:d:h:m:s]: 00:095:19:33:20
Block: 1092557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68519 RingCT/type: yes/0
Extra: 0166d5b7aeecd9ba8a9dd0c6cac14ef518788f0f838c78454eafc0bbfc595772f502110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35352dbb4b594f0e34aed4966aeeb61f6df1030919b6976b9eb8fc21886d9ced 0.600000000000 1567326 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": 1092567, "vin": [ { "gen": { "height": 1092557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35352dbb4b594f0e34aed4966aeeb61f6df1030919b6976b9eb8fc21886d9ced" } } ], "extra": [ 1, 102, 213, 183, 174, 236, 217, 186, 138, 157, 208, 198, 202, 193, 78, 245, 24, 120, 143, 15, 131, 140, 120, 69, 78, 175, 192, 187, 252, 89, 87, 114, 245, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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