Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4387384db44fcd17431a5c4d348e0af3a3038061c23f2cd3b89a5d3dd4e312c9

Tx prefix hash: 8482095d7f05e230c31b3d53ea033485e5a22aaa84d6ca0844c8e516a365dd82
Tx public key: 038e1a7d3575befe784c9c28b7c2fa556167bb7e679737ca45ea75eb3d70be38
Timestamp: 1714181053 Timestamp [UCT]: 2024-04-27 01:24:13 Age [y:d:h:m:s]: 00:345:14:04:03
Block: 1009302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247049 RingCT/type: yes/0
Extra: 01038e1a7d3575befe784c9c28b7c2fa556167bb7e679737ca45ea75eb3d70be380211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f358ff035ad3ebac50501dabf68316a1a253e639a3b311d64b5f0688d97ffc7d 0.600000000000 1470938 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": 1009312, "vin": [ { "gen": { "height": 1009302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f358ff035ad3ebac50501dabf68316a1a253e639a3b311d64b5f0688d97ffc7d" } } ], "extra": [ 1, 3, 142, 26, 125, 53, 117, 190, 254, 120, 76, 156, 40, 183, 194, 250, 85, 97, 103, 187, 126, 103, 151, 55, 202, 69, 234, 117, 235, 61, 112, 190, 56, 2, 17, 0, 0, 0, 3, 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