Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b1de9b8d730ba7367c7931b20d1296639d4482e0ea35f276881f71cf7de3596

Tx prefix hash: cc63ac6e110013106b02e8b3fab2feb9f74d8e42e3f18645ad34592b66ad95df
Tx public key: 1929db2f0caa5a2dfded6ec9138370e5250efa80324202ae4b871c7515fa25c1
Timestamp: 1703577056 Timestamp [UCT]: 2023-12-26 07:50:56 Age [y:d:h:m:s]: 01:319:14:13:31
Block: 921398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487259 RingCT/type: yes/0
Extra: 011929db2f0caa5a2dfded6ec9138370e5250efa80324202ae4b871c7515fa25c102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62f3cac28b7b528820543aa1f438f7d38a3700cd24538173d3253adc3e23b2a0 0.600000000000 1379086 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": 921408, "vin": [ { "gen": { "height": 921398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62f3cac28b7b528820543aa1f438f7d38a3700cd24538173d3253adc3e23b2a0" } } ], "extra": [ 1, 25, 41, 219, 47, 12, 170, 90, 45, 253, 237, 110, 201, 19, 131, 112, 229, 37, 14, 250, 128, 50, 66, 2, 174, 75, 135, 28, 117, 21, 250, 37, 193, 2, 17, 0, 0, 0, 2, 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