Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51b38e4f95642a35c368eb0972f6d2e868dfae158fab5f0b4c204e04e7e265c0

Tx prefix hash: 04bc7421c6ad3f13cc66caa4eaac6287b48bf5793f69a57d179f038c676d55b9
Tx public key: ff3ee97d427a3154c29e110ad9fcacd98ce8aec90b05988cf919b8ad4edda6d5
Timestamp: 1752913616 Timestamp [UCT]: 2025-07-19 08:26:56 Age [y:d:h:m:s]: 00:169:08:07:00
Block: 1328698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119900 RingCT/type: yes/0
Extra: 01ff3ee97d427a3154c29e110ad9fcacd98ce8aec90b05988cf919b8ad4edda6d5021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e4c812c9ece3d5d212c11feaddcbf9cc6bb63c2f403890c85d5dea8280bdd2d 0.600000000000 1816461 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": 1328708, "vin": [ { "gen": { "height": 1328698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e4c812c9ece3d5d212c11feaddcbf9cc6bb63c2f403890c85d5dea8280bdd2d" } } ], "extra": [ 1, 255, 62, 233, 125, 66, 122, 49, 84, 194, 158, 17, 10, 217, 252, 172, 217, 140, 232, 174, 201, 11, 5, 152, 140, 249, 25, 184, 173, 78, 221, 166, 213, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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