Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a6ce7bdcd7223c766a8b2ed947b2348f3dad51718e8f0fb3d3e7009972bb2e9

Tx prefix hash: dcc45da2eca5ec53325a4ba1629f84a512db57d25164f90030d064e9de731795
Tx public key: 3986e589e8aa1feaadf6934bdab0f8271b1128fe8df910b1f3087008b25b718c
Timestamp: 1751177919 Timestamp [UCT]: 2025-06-29 06:18:39 Age [y:d:h:m:s]: 00:142:11:33:29
Block: 1315013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99960 RingCT/type: yes/0
Extra: 013986e589e8aa1feaadf6934bdab0f8271b1128fe8df910b1f3087008b25b718c021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe2b057c9a924519eb10918598d090bcc93376f9b1910eb6235ae17a1c3885cb 0.600000000000 1802666 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": 1315023, "vin": [ { "gen": { "height": 1315013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe2b057c9a924519eb10918598d090bcc93376f9b1910eb6235ae17a1c3885cb" } } ], "extra": [ 1, 57, 134, 229, 137, 232, 170, 31, 234, 173, 246, 147, 75, 218, 176, 248, 39, 27, 17, 40, 254, 141, 249, 16, 177, 243, 8, 112, 8, 178, 91, 113, 140, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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