Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0775d1cffdc97f9feb3aef854ee5acd18d42a85456926952c40fe422f1b5457e

Tx prefix hash: c15bcffd0c38713babb10633b97470a48692ed8fa835abf69017d7c266430b6d
Tx public key: 7d8bb9cbe130e9f68e0c548dcd89d0cdb7e3e5d301bb8f7fbedca143f3d17294
Timestamp: 1751556554 Timestamp [UCT]: 2025-07-03 15:29:14 Age [y:d:h:m:s]: 00:133:13:16:44
Block: 1318038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93674 RingCT/type: yes/0
Extra: 017d8bb9cbe130e9f68e0c548dcd89d0cdb7e3e5d301bb8f7fbedca143f3d17294021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec323d82f4572e8b0fd8086a15e252be28f9f89f627c702bebbde7f5b8031080 0.600000000000 1805709 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": 1318048, "vin": [ { "gen": { "height": 1318038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec323d82f4572e8b0fd8086a15e252be28f9f89f627c702bebbde7f5b8031080" } } ], "extra": [ 1, 125, 139, 185, 203, 225, 48, 233, 246, 142, 12, 84, 141, 205, 137, 208, 205, 183, 227, 229, 211, 1, 187, 143, 127, 190, 220, 161, 67, 243, 209, 114, 148, 2, 17, 0, 0, 0, 8, 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