Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16a53555e5c44a027261dbf9760c7aa43d15749b23c2569f5701bef0d4062325

Tx prefix hash: 33876591da3d2fbc207b23793b59b53b7cf97e64863cad5554b6885d79979ca0
Tx public key: f2f35e46e2488caeb0f8d4198b8e925e01b1f1d3ad3d96464aeff64085d16d3a
Timestamp: 1761803590 Timestamp [UCT]: 2025-10-30 05:53:10 Age [y:d:h:m:s]: 00:007:16:22:24
Block: 1401015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5490 RingCT/type: yes/0
Extra: 01f2f35e46e2488caeb0f8d4198b8e925e01b1f1d3ad3d96464aeff64085d16d3a021100000003df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b2e6adb4c1ee286497a641432f6b23945683032367a808a58c59d449410b621 0.600000000000 1889334 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": 1401025, "vin": [ { "gen": { "height": 1401015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b2e6adb4c1ee286497a641432f6b23945683032367a808a58c59d449410b621" } } ], "extra": [ 1, 242, 243, 94, 70, 226, 72, 140, 174, 176, 248, 212, 25, 139, 142, 146, 94, 1, 177, 241, 211, 173, 61, 150, 70, 74, 239, 246, 64, 133, 209, 109, 58, 2, 17, 0, 0, 0, 3, 223, 90, 36, 122, 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