Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d221a337e091c810145533a9150c5ad235ef7597cdaab78511b410ba3f9b2b1a

Tx prefix hash: de6790d0af5499c3f7d3462ea6b55b15b740f2c1496dc88f0beba659e08c8caf
Tx public key: 202ee85f660a89f48406712f1ef93abb2477d79e85e4430b0688e22eb274d3aa
Timestamp: 1700077145 Timestamp [UCT]: 2023-11-15 19:39:05 Age [y:d:h:m:s]: 01:140:15:17:37
Block: 892380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361697 RingCT/type: yes/0
Extra: 01202ee85f660a89f48406712f1ef93abb2477d79e85e4430b0688e22eb274d3aa021100000003c5452960000000000000000000

1 output(s) for total of 0.677914011000 dcy

stealth address amount amount idx
00: e1a567a5f6ee2409137ed3c271809f7885c1b6166154fbd6f3d5e7d848f8708b 0.677914011000 1348499 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": 892390, "vin": [ { "gen": { "height": 892380 } } ], "vout": [ { "amount": 677914011, "target": { "key": "e1a567a5f6ee2409137ed3c271809f7885c1b6166154fbd6f3d5e7d848f8708b" } } ], "extra": [ 1, 32, 46, 232, 95, 102, 10, 137, 244, 132, 6, 113, 47, 30, 249, 58, 187, 36, 119, 215, 158, 133, 228, 67, 11, 6, 136, 226, 46, 178, 116, 211, 170, 2, 17, 0, 0, 0, 3, 197, 69, 41, 96, 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