Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f861520d44707e2cad192d8c139eee604a5bc6341d851644778744f0202ce15

Tx prefix hash: 73d305604c87cdc20b0a48ef796ab20b6e0b93f3df75368a8b99d901c21c1acc
Tx public key: 73c8d28874562dd1d54bda31bf614348fc7a7a75ef6b45d316c0fb232d0b63d9
Timestamp: 1755454279 Timestamp [UCT]: 2025-08-17 18:11:19 Age [y:d:h:m:s]: 00:095:10:16:45
Block: 1348667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68033 RingCT/type: yes/0
Extra: 0173c8d28874562dd1d54bda31bf614348fc7a7a75ef6b45d316c0fb232d0b63d9021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7669d3e9e6bbf9934aeb6f7132471a8726c0245554d5f0e698813ceb5a66fd3a 0.600000000000 1836594 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": 1348677, "vin": [ { "gen": { "height": 1348667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7669d3e9e6bbf9934aeb6f7132471a8726c0245554d5f0e698813ceb5a66fd3a" } } ], "extra": [ 1, 115, 200, 210, 136, 116, 86, 45, 209, 213, 75, 218, 49, 191, 97, 67, 72, 252, 122, 122, 117, 239, 107, 69, 211, 22, 192, 251, 35, 45, 11, 99, 217, 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