Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 353bfcbc2c54b1017c27ad52a52605a2f82a12dedacac5db93b39eb2dc609a0f

Tx prefix hash: 6c15fb486a694c91e6ebc192872bd8aed786af3777d5669ba78686360d1ba7e7
Tx public key: d4b16a81501a809809b851743b6f3eb9290421624101cd1b46f7c2578055355d
Timestamp: 1702710928 Timestamp [UCT]: 2023-12-16 07:15:28 Age [y:d:h:m:s]: 01:035:20:42:09
Block: 914217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286949 RingCT/type: yes/0
Extra: 01d4b16a81501a809809b851743b6f3eb9290421624101cd1b46f7c2578055355d02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a356935e2f96d38206046bcdfab486c4e210c3ca559c8fd37733e76a68dcb1f5 0.600000000000 1371503 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": 914227, "vin": [ { "gen": { "height": 914217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a356935e2f96d38206046bcdfab486c4e210c3ca559c8fd37733e76a68dcb1f5" } } ], "extra": [ 1, 212, 177, 106, 129, 80, 26, 128, 152, 9, 184, 81, 116, 59, 111, 62, 185, 41, 4, 33, 98, 65, 1, 205, 27, 70, 247, 194, 87, 128, 85, 53, 93, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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