Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2b74fa56711f20219e617687833bcb6580bb231f793f8a4086950aefb3b8643

Tx prefix hash: a1f14f30353e52681b904895fccf290c9ef52904d992b8c261112f8fdeaab7b7
Tx public key: d3febc49986c80b7d9af61d442e5a483f108da30b845bc5be9c7f1bfca30a1d5
Timestamp: 1714106121 Timestamp [UCT]: 2024-04-26 04:35:21 Age [y:d:h:m:s]: 00:199:05:25:05
Block: 1008689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142606 RingCT/type: yes/0
Extra: 01d3febc49986c80b7d9af61d442e5a483f108da30b845bc5be9c7f1bfca30a1d502110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01a56313e66bffda827de548e343362958cb83981fc5527cb9e99f6cecdf09a3 0.600000000000 1470165 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": 1008699, "vin": [ { "gen": { "height": 1008689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01a56313e66bffda827de548e343362958cb83981fc5527cb9e99f6cecdf09a3" } } ], "extra": [ 1, 211, 254, 188, 73, 152, 108, 128, 183, 217, 175, 97, 212, 66, 229, 164, 131, 241, 8, 218, 48, 184, 69, 188, 91, 233, 199, 241, 191, 202, 48, 161, 213, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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