Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 393c207136f3b3127ad087ca289c4e2f56e2b9751707ccf99d167fed0f8f40e5

Tx prefix hash: 93437b7b7aec988629871e72a5c2a7186d7838dc5fb9b23f0a579e777bf57493
Tx public key: f00835d40a3d1992d38aeb49c9aa3523567c3b889d7be387c1b9f5d428033f91
Timestamp: 1732905400 Timestamp [UCT]: 2024-11-29 18:36:40 Age [y:d:h:m:s]: 00:110:03:39:21
Block: 1164455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78542 RingCT/type: yes/0
Extra: 01f00835d40a3d1992d38aeb49c9aa3523567c3b889d7be387c1b9f5d428033f910211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9eab33a7dbe1de0f3ee14187ceee89f4a164b116d798523d9e490b827a9027b7 0.600000000000 1650128 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": 1164465, "vin": [ { "gen": { "height": 1164455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9eab33a7dbe1de0f3ee14187ceee89f4a164b116d798523d9e490b827a9027b7" } } ], "extra": [ 1, 240, 8, 53, 212, 10, 61, 25, 146, 211, 138, 235, 73, 201, 170, 53, 35, 86, 124, 59, 136, 157, 123, 227, 135, 193, 185, 245, 212, 40, 3, 63, 145, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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