Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edb15b6a88b4e9849cfcde9712dac63f9e5ce6a629328e164b5c5d153c6efbf8

Tx prefix hash: d69b0fbd8dc3974cce1047e42263e7c6e9079ec38f010973c363e893e38ec465
Tx public key: 95da470f7e6d284430cb2f95c5f069440fc5e5a3ab1ef59422d023305304eedb
Timestamp: 1703668443 Timestamp [UCT]: 2023-12-27 09:14:03 Age [y:d:h:m:s]: 01:117:05:37:13
Block: 922160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344904 RingCT/type: yes/0
Extra: 0195da470f7e6d284430cb2f95c5f069440fc5e5a3ab1ef59422d023305304eedb021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3f80add201c0ecbed95d7aee1161ca324c81ccb3c1edc6c05ff2db1cb45c126 0.600000000000 1379854 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": 922170, "vin": [ { "gen": { "height": 922160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3f80add201c0ecbed95d7aee1161ca324c81ccb3c1edc6c05ff2db1cb45c126" } } ], "extra": [ 1, 149, 218, 71, 15, 126, 109, 40, 68, 48, 203, 47, 149, 197, 240, 105, 68, 15, 197, 229, 163, 171, 30, 245, 148, 34, 208, 35, 48, 83, 4, 238, 219, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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