Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42eab216bd9be6b10cc8ae0f748dc8e056777f94add73457616457732faf9a34

Tx prefix hash: 402655eddb436459ec4e8c62a4d01001c4262297f30684fce0af52e5f5839bc2
Tx public key: 4f06f2639164875318be2f67f41ea96869325c3dbc2da5d1f5a305cc7ffb69d8
Timestamp: 1759982505 Timestamp [UCT]: 2025-10-09 04:01:45 Age [y:d:h:m:s]: 00:043:10:07:09
Block: 1385916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31079 RingCT/type: yes/0
Extra: 014f06f2639164875318be2f67f41ea96869325c3dbc2da5d1f5a305cc7ffb69d802110000000ba5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9c7f18f82aa1f3b4b409c08d1493f1c1830c02abb3d5142507dd83e229162a1 0.600000000000 1874079 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": 1385926, "vin": [ { "gen": { "height": 1385916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9c7f18f82aa1f3b4b409c08d1493f1c1830c02abb3d5142507dd83e229162a1" } } ], "extra": [ 1, 79, 6, 242, 99, 145, 100, 135, 83, 24, 190, 47, 103, 244, 30, 169, 104, 105, 50, 92, 61, 188, 45, 165, 209, 245, 163, 5, 204, 127, 251, 105, 216, 2, 17, 0, 0, 0, 11, 165, 220, 205, 121, 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