Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3896eee549cf3e6ed8362b1765f5d822c0f09d0656a497f67d80a109e4741685

Tx prefix hash: 357d252057c4bc2237d4e481c7969da51d778845b005e8ef5e8e8f1510eaaef0
Tx public key: 9c705e01e8ae98339f021c506df0eb1b7b480007fd6f027155114268a7c298d9
Timestamp: 1727425222 Timestamp [UCT]: 2024-09-27 08:20:22 Age [y:d:h:m:s]: 00:230:00:26:24
Block: 1119121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164222 RingCT/type: yes/0
Extra: 019c705e01e8ae98339f021c506df0eb1b7b480007fd6f027155114268a7c298d9021100000009e914dd15000000000000000000

1 output(s) for total of 0.600200000000 dcy

stealth address amount amount idx
00: 88626074d7f144ebd145e2b969c541d8d88319474110fecadc68245df54d788e 0.600200000000 1600558 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": 1119131, "vin": [ { "gen": { "height": 1119121 } } ], "vout": [ { "amount": 600200000, "target": { "key": "88626074d7f144ebd145e2b969c541d8d88319474110fecadc68245df54d788e" } } ], "extra": [ 1, 156, 112, 94, 1, 232, 174, 152, 51, 159, 2, 28, 80, 109, 240, 235, 27, 123, 72, 0, 7, 253, 111, 2, 113, 85, 17, 66, 104, 167, 194, 152, 217, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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