Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 631efb5f324575f51ee282a5144d5d6117b8c0041601de46cfa0a809f5025d57

Tx prefix hash: 534285bf0f10f26e54845cf2cc67c9aedbbbc157bdda30b4e5c3c5c4a7f5b2af
Tx public key: 3c20a779e4966a6cca05be2b49e9a7eeacea48464734f6e9d98b86ebd0ceb706
Timestamp: 1753023122 Timestamp [UCT]: 2025-07-20 14:52:02 Age [y:d:h:m:s]: 00:074:04:58:01
Block: 1329590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51774 RingCT/type: yes/0
Extra: 013c20a779e4966a6cca05be2b49e9a7eeacea48464734f6e9d98b86ebd0ceb70602110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2d95341bc37e2cb61af050a49c9f0406bef1cf8f192b9101a2d13d05117d1bd 0.600000000000 1817367 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": 1329600, "vin": [ { "gen": { "height": 1329590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2d95341bc37e2cb61af050a49c9f0406bef1cf8f192b9101a2d13d05117d1bd" } } ], "extra": [ 1, 60, 32, 167, 121, 228, 150, 106, 108, 202, 5, 190, 43, 73, 233, 167, 238, 172, 234, 72, 70, 71, 52, 246, 233, 217, 139, 134, 235, 208, 206, 183, 6, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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