Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2bcb4cc8829f30f48aabd960e3125006a5846f7a78c7b9b1c371a3163d63f99

Tx prefix hash: ec875e0ab1dfb852162a122022b06f1c370fce1cc279fe1651a366b9c4419c26
Tx public key: 9fff0d590760df81a7aaf7dfda304249c4d32d9f29268d8f9d6693675a46560d
Timestamp: 1740480224 Timestamp [UCT]: 2025-02-25 10:43:44 Age [y:d:h:m:s]: 00:340:06:14:36
Block: 1226881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240868 RingCT/type: yes/0
Extra: 019fff0d590760df81a7aaf7dfda304249c4d32d9f29268d8f9d6693675a46560d0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b62e6c49edab686e3246a16d3006a76b62b85e3e29bb2737a4bc987783673c6 0.600000000000 1713754 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": 1226891, "vin": [ { "gen": { "height": 1226881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b62e6c49edab686e3246a16d3006a76b62b85e3e29bb2737a4bc987783673c6" } } ], "extra": [ 1, 159, 255, 13, 89, 7, 96, 223, 129, 167, 170, 247, 223, 218, 48, 66, 73, 196, 211, 45, 159, 41, 38, 141, 143, 157, 102, 147, 103, 90, 70, 86, 13, 2, 17, 0, 0, 0, 5, 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