Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7fdfa91c11a740a1c691e2b05e0b97b0f74b71842c6ce34c0464ef80ab96f70

Tx prefix hash: 76a8f88c096488ccf472421795eb865134bf0693e044b640f2618d30629ce521
Tx public key: 4bdb83df51eddf1e38bc318211dc97ab4c779d7ad852b1683643b6cb1f10b5d2
Timestamp: 1703707622 Timestamp [UCT]: 2023-12-27 20:07:02 Age [y:d:h:m:s]: 01:113:15:01:08
Block: 922481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342332 RingCT/type: yes/0
Extra: 014bdb83df51eddf1e38bc318211dc97ab4c779d7ad852b1683643b6cb1f10b5d202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c260d1b78c411528309cfd2501836746fd9b1a0f22f5162e9b3a0272030f9df 0.600000000000 1380179 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": 922491, "vin": [ { "gen": { "height": 922481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c260d1b78c411528309cfd2501836746fd9b1a0f22f5162e9b3a0272030f9df" } } ], "extra": [ 1, 75, 219, 131, 223, 81, 237, 223, 30, 56, 188, 49, 130, 17, 220, 151, 171, 76, 119, 157, 122, 216, 82, 177, 104, 54, 67, 182, 203, 31, 16, 181, 210, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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