Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20ed37e85d0cbe1e741dce579697fb9e9406b743d65a2974835c60275edcf3df

Tx prefix hash: 79afb161a5fd51ef8c2381ddd3a42f47738ddc1d61c8b759c33371394c5e224d
Tx public key: cd7a00928308a8f2e52ae275018b4781ef6af1f94a6a2e60ffdb8bd0e0683b1b
Timestamp: 1657230241 Timestamp [UCT]: 2022-07-07 21:44:01 Age [y:d:h:m:s]: 02:179:19:35:18
Block: 538877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 649853 RingCT/type: yes/0
Extra: 01cd7a00928308a8f2e52ae275018b4781ef6af1f94a6a2e60ffdb8bd0e0683b1b021100000003bf7ee4e7000000000000000000

1 output(s) for total of 10.057196813000 dcy

stealth address amount amount idx
00: cd867ee1597cf707a0440d7eaa19a8a714f24b916627b6d7900807089bf92fcc 10.057196813000 968928 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": 538887, "vin": [ { "gen": { "height": 538877 } } ], "vout": [ { "amount": 10057196813, "target": { "key": "cd867ee1597cf707a0440d7eaa19a8a714f24b916627b6d7900807089bf92fcc" } } ], "extra": [ 1, 205, 122, 0, 146, 131, 8, 168, 242, 229, 42, 226, 117, 1, 139, 71, 129, 239, 106, 241, 249, 74, 106, 46, 96, 255, 219, 139, 208, 224, 104, 59, 27, 2, 17, 0, 0, 0, 3, 191, 126, 228, 231, 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