Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b39bf5bc28a4ce06e772e237a62bfb5a294c6db9afa76506554f64fd0a3cf43

Tx prefix hash: d0911c2720da94f244c055844eb4e20924c7ce9877bb2e24049e5892aaf85848
Tx public key: d7cab70b1c6d62c418740564bb54ff17c99ecad5acb015eb9a651b099a77c40c
Timestamp: 1703593117 Timestamp [UCT]: 2023-12-26 12:18:37 Age [y:d:h:m:s]: 02:034:03:49:06
Block: 921538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544038 RingCT/type: yes/0
Extra: 01d7cab70b1c6d62c418740564bb54ff17c99ecad5acb015eb9a651b099a77c40c02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 384abc6c9d5fcd2ed3f2c9280133df5920daa64483f9ad2e2fe0e2ebfa6d20e3 0.600000000000 1379226 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": 921548, "vin": [ { "gen": { "height": 921538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "384abc6c9d5fcd2ed3f2c9280133df5920daa64483f9ad2e2fe0e2ebfa6d20e3" } } ], "extra": [ 1, 215, 202, 183, 11, 28, 109, 98, 196, 24, 116, 5, 100, 187, 84, 255, 23, 201, 158, 202, 213, 172, 176, 21, 235, 154, 101, 27, 9, 154, 119, 196, 12, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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