Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 587ceec307f2c38420fb0b5a1d223dd2ad1e957092ce184d532f06b51e2edc64

Tx prefix hash: 0274ad51bc2f68ddc4d24b6c2b0a1ae306ed8e882978828a72adbd6ea507c394
Tx public key: d3fa81e58a8f30f881f9dcb68c33bea40d63a421285b11501b8f7a4796308301
Timestamp: 1752461604 Timestamp [UCT]: 2025-07-14 02:53:24 Age [y:d:h:m:s]: 00:037:16:12:58
Block: 1325023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25749 RingCT/type: yes/0
Extra: 01d3fa81e58a8f30f881f9dcb68c33bea40d63a421285b11501b8f7a4796308301021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f0ba5f0e4d2a06f903a27e0b531fcf04c7a3c0c91c005830d8e0bfd45d5ff34 0.600000000000 1812768 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": 1325033, "vin": [ { "gen": { "height": 1325023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f0ba5f0e4d2a06f903a27e0b531fcf04c7a3c0c91c005830d8e0bfd45d5ff34" } } ], "extra": [ 1, 211, 250, 129, 229, 138, 143, 48, 248, 129, 249, 220, 182, 140, 51, 190, 164, 13, 99, 164, 33, 40, 91, 17, 80, 27, 143, 122, 71, 150, 48, 131, 1, 2, 17, 0, 0, 0, 6, 191, 81, 178, 162, 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