Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b6a23d7719c8e13a5f3101e18b1f5387603e194833529bd6cff83da20720d51

Tx prefix hash: 4eb2288642e9ef0845a40c483f1d0e86102696cac0555d08f77fe8269fef0483
Tx public key: 573b2a8fd265c75e2584f7f9d9667f798aeefa288f75516bd1fbfbc59fad796c
Timestamp: 1638129517 Timestamp [UCT]: 2021-11-28 19:58:37 Age [y:d:h:m:s]: 03:337:11:44:44
Block: 384175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1017612 RingCT/type: yes/0
Extra: 01573b2a8fd265c75e2584f7f9d9667f798aeefa288f75516bd1fbfbc59fad796c021100000003f6cc1430000000000000000000

1 output(s) for total of 32.740209757000 dcy

stealth address amount amount idx
00: b0fcb36f1ff82e39cce1be03d6f258e9ade3a8f0344447a3f9e8a8752b176747 32.740209757000 775470 of 0

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": 384185, "vin": [ { "gen": { "height": 384175 } } ], "vout": [ { "amount": 32740209757, "target": { "key": "b0fcb36f1ff82e39cce1be03d6f258e9ade3a8f0344447a3f9e8a8752b176747" } } ], "extra": [ 1, 87, 59, 42, 143, 210, 101, 199, 94, 37, 132, 247, 249, 217, 102, 127, 121, 138, 238, 250, 40, 143, 117, 81, 107, 209, 251, 251, 197, 159, 173, 121, 108, 2, 17, 0, 0, 0, 3, 246, 204, 20, 48, 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