Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92abc44fc2a17935c40cc4cab691f45a3068990da59ae4ee0f155bb834c0bd9e

Tx prefix hash: 08bea1cb8646950e80792dbc690f8888093729e2e30e0b45c61ba4d0a0381622
Tx public key: a08d26cf69de6bad0fd71487c2fc52e8b1d8b2f9266e4a36c8c7f5a6e0127318
Timestamp: 1738243688 Timestamp [UCT]: 2025-01-30 13:28:08 Age [y:d:h:m:s]: 00:042:23:07:56
Block: 1208382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30750 RingCT/type: yes/0
Extra: 01a08d26cf69de6bad0fd71487c2fc52e8b1d8b2f9266e4a36c8c7f5a6e0127318021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 131ba5208fd3b199b95696b511a443bb75126c5769cd0567d4aaca85c8e117cb 0.600000000000 1695113 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": 1208392, "vin": [ { "gen": { "height": 1208382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "131ba5208fd3b199b95696b511a443bb75126c5769cd0567d4aaca85c8e117cb" } } ], "extra": [ 1, 160, 141, 38, 207, 105, 222, 107, 173, 15, 215, 20, 135, 194, 252, 82, 232, 177, 216, 178, 249, 38, 110, 74, 54, 200, 199, 245, 166, 224, 18, 115, 24, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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