Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b98f8bec17f7019c172a355c42c79630d911215dc80f23635a6f4c9bc40de772

Tx prefix hash: 25845f3d3863fb272d9a767e8103630b2ba379944275ca5e4e4175734224d887
Tx public key: 459c63ff2352e19f84607c43cfafb1e33de0a1d2b36cd9a2b12370c34f2edd91
Timestamp: 1752176678 Timestamp [UCT]: 2025-07-10 19:44:38 Age [y:d:h:m:s]: 00:206:18:28:15
Block: 1322812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146291 RingCT/type: yes/0
Extra: 01459c63ff2352e19f84607c43cfafb1e33de0a1d2b36cd9a2b12370c34f2edd91021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 142c1d367a49d8534eb453404615e95e3386ad9df0c0d2a01e7f03dc9a0f399a 0.600000000000 1810543 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": 1322822, "vin": [ { "gen": { "height": 1322812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "142c1d367a49d8534eb453404615e95e3386ad9df0c0d2a01e7f03dc9a0f399a" } } ], "extra": [ 1, 69, 156, 99, 255, 35, 82, 225, 159, 132, 96, 124, 67, 207, 175, 177, 227, 61, 224, 161, 210, 179, 108, 217, 162, 177, 35, 112, 195, 79, 46, 221, 145, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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