Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 947efdc5bef39e12d3243b3fa5478ac4073641e71c7425fc2c84db8bf3a19634

Tx prefix hash: 7cdd53a0f6a0de4ec87a8731fa3115515e45ab05cbd682744a8e5a8ea2656b2e
Tx public key: 086acc12255822f05356d9a45b2bce91ce204cc45fc19fbadb71a80d1a0e1e49
Timestamp: 1751799261 Timestamp [UCT]: 2025-07-06 10:54:21 Age [y:d:h:m:s]: 00:180:23:41:23
Block: 1319884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127812 RingCT/type: yes/0
Extra: 01086acc12255822f05356d9a45b2bce91ce204cc45fc19fbadb71a80d1a0e1e49021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7cde216aa761f3c3a03c8f21c912da24072a35e88a6803631753a3c2dfbcd87 0.600000000000 1807577 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": 1319894, "vin": [ { "gen": { "height": 1319884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7cde216aa761f3c3a03c8f21c912da24072a35e88a6803631753a3c2dfbcd87" } } ], "extra": [ 1, 8, 106, 204, 18, 37, 88, 34, 240, 83, 86, 217, 164, 91, 43, 206, 145, 206, 32, 76, 196, 95, 193, 159, 186, 219, 113, 168, 13, 26, 14, 30, 73, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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