Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f559c7ae25319e61297d2c2c52fc98922d115327ec9320599f29a6ff19925c7a

Tx prefix hash: 5bbe76f1bb95cefb61454bc4a425602cd3e03becf630d2a9dcead1aab9a876e6
Tx public key: 197df76722528e4fb5562b11538d2c8d0b6410fa87ac5eb070cb23f95c84ac20
Timestamp: 1745821203 Timestamp [UCT]: 2025-04-28 06:20:03 Age [y:d:h:m:s]: 00:010:21:04:04
Block: 1271119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7767 RingCT/type: yes/0
Extra: 01197df76722528e4fb5562b11538d2c8d0b6410fa87ac5eb070cb23f95c84ac200211000000089f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bd58c810e5d9b1eafa5f6cfb5552a4603c24c53b0ced4dd54c21c3e7ea0a8d8 0.600000000000 1758370 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": 1271129, "vin": [ { "gen": { "height": 1271119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bd58c810e5d9b1eafa5f6cfb5552a4603c24c53b0ced4dd54c21c3e7ea0a8d8" } } ], "extra": [ 1, 25, 125, 247, 103, 34, 82, 142, 79, 181, 86, 43, 17, 83, 141, 44, 141, 11, 100, 16, 250, 135, 172, 94, 176, 112, 203, 35, 249, 92, 132, 172, 32, 2, 17, 0, 0, 0, 8, 159, 159, 230, 140, 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