Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b248d98bcb302969fdf9228eeaa7bb0fdbc6a40f76e3ee267915604e67344283

Tx prefix hash: 525fa4ffbdb7859900e2cb680fe552b7e7bb1b60a9f56d89e8abcf3b31a9b4ca
Tx public key: 8f77dbbd1eee2ec49413a5a593c3ea91c74104f3fb6ff7d5593241646d11b095
Timestamp: 1759316847 Timestamp [UCT]: 2025-10-01 11:07:27 Age [y:d:h:m:s]: 00:093:23:37:49
Block: 1380387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67316 RingCT/type: yes/0
Extra: 018f77dbbd1eee2ec49413a5a593c3ea91c74104f3fb6ff7d5593241646d11b095021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72c555913af47b7172f6f9582da004e1cf4d0a19ab0cd669bb0870cb349e940c 0.600000000000 1868498 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": 1380397, "vin": [ { "gen": { "height": 1380387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72c555913af47b7172f6f9582da004e1cf4d0a19ab0cd669bb0870cb349e940c" } } ], "extra": [ 1, 143, 119, 219, 189, 30, 238, 46, 196, 148, 19, 165, 165, 147, 195, 234, 145, 199, 65, 4, 243, 251, 111, 247, 213, 89, 50, 65, 100, 109, 17, 176, 149, 2, 17, 0, 0, 0, 1, 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