Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db732814baadca0979c870600bf392efdf7448fa7846168c92792fff2a9f8741

Tx prefix hash: c95700a7e324f38193621f16da57c91d42271f583be2a7797907d9788485abe6
Tx public key: 71c1355d0de25d1ce65c72ad9c6ba293863b0d22c3b4966d6f1a00a0394e9fd5
Timestamp: 1722510576 Timestamp [UCT]: 2024-08-01 11:09:36 Age [y:d:h:m:s]: 00:205:20:01:59
Block: 1078371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146961 RingCT/type: yes/0
Extra: 0171c1355d0de25d1ce65c72ad9c6ba293863b0d22c3b4966d6f1a00a0394e9fd502110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c2aa93737cd879b6a2e6d5120a820803861450e3740db3b1fbe1d35e7b3c873 0.600000000000 1550948 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": 1078381, "vin": [ { "gen": { "height": 1078371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c2aa93737cd879b6a2e6d5120a820803861450e3740db3b1fbe1d35e7b3c873" } } ], "extra": [ 1, 113, 193, 53, 93, 13, 226, 93, 28, 230, 92, 114, 173, 156, 107, 162, 147, 134, 59, 13, 34, 195, 180, 150, 109, 111, 26, 0, 160, 57, 78, 159, 213, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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