Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f70248c92547d2ccb60103b97b316054633c9a740c023448947503c9dc08ed9b

Tx prefix hash: 297885b4d08629b2f9660ab75b970c6fd5f58614c0dfdd1a6c4fd31de39e217a
Tx public key: 9b0ad0a0681c875826c2baafcf93877c5aa2b951095c4d667e7649dd845fd589
Timestamp: 1751684877 Timestamp [UCT]: 2025-07-05 03:07:57 Age [y:d:h:m:s]: 00:138:15:49:43
Block: 1319014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97416 RingCT/type: yes/0
Extra: 019b0ad0a0681c875826c2baafcf93877c5aa2b951095c4d667e7649dd845fd5890211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a395536730c75286229d4a82c138c83906a73ba83953891329d0aa5c9252972 0.600000000000 1806703 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": 1319024, "vin": [ { "gen": { "height": 1319014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a395536730c75286229d4a82c138c83906a73ba83953891329d0aa5c9252972" } } ], "extra": [ 1, 155, 10, 208, 160, 104, 28, 135, 88, 38, 194, 186, 175, 207, 147, 135, 124, 90, 162, 185, 81, 9, 92, 77, 102, 126, 118, 73, 221, 132, 95, 213, 137, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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