Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a1116a1119b56c2c713c1d4fe11019036746c63b62a1a1aff1026d1e6b158ad

Tx prefix hash: dde06d0f7991c4d84a1a8a53d0585dd1e4d1a44befec632323baa9e3fdb28e3f
Tx public key: acf0e74ad24f217eb65bbdb1186f886987974f91c2321e8dee2bd04c92be2897
Timestamp: 1703645280 Timestamp [UCT]: 2023-12-27 02:48:00 Age [y:d:h:m:s]: 01:315:21:30:42
Block: 921963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484594 RingCT/type: yes/0
Extra: 01acf0e74ad24f217eb65bbdb1186f886987974f91c2321e8dee2bd04c92be289702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 932c97b2fd62d3256b0c89aabcb080b231c5f1b4ffb492e3203c45653db0cf93 0.600000000000 1379657 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": 921973, "vin": [ { "gen": { "height": 921963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "932c97b2fd62d3256b0c89aabcb080b231c5f1b4ffb492e3203c45653db0cf93" } } ], "extra": [ 1, 172, 240, 231, 74, 210, 79, 33, 126, 182, 91, 189, 177, 24, 111, 136, 105, 135, 151, 79, 145, 194, 50, 30, 141, 238, 43, 208, 76, 146, 190, 40, 151, 2, 17, 0, 0, 0, 2, 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