Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 565760b4193e643bd34d4311f2ae1b608eb44ccc5e6482b7509e3fd0a7fb9a9d

Tx prefix hash: 75355e29169261274b855c9a5064b028ea6db4caacf38b41a294bfe73f6ee210
Tx public key: a85a5e8247c80207ac094da8c43ace0fd3831c466102d445de74b104d122a039
Timestamp: 1734197516 Timestamp [UCT]: 2024-12-14 17:31:56 Age [y:d:h:m:s]: 00:187:11:03:31
Block: 1175170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133657 RingCT/type: yes/0
Extra: 01a85a5e8247c80207ac094da8c43ace0fd3831c466102d445de74b104d122a039021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd40d32a48cdc515c57c30b3dbaf088a496b7b1508ecfd3629070be14c47e7a7 0.600000000000 1661411 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": 1175180, "vin": [ { "gen": { "height": 1175170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd40d32a48cdc515c57c30b3dbaf088a496b7b1508ecfd3629070be14c47e7a7" } } ], "extra": [ 1, 168, 90, 94, 130, 71, 200, 2, 7, 172, 9, 77, 168, 196, 58, 206, 15, 211, 131, 28, 70, 97, 2, 212, 69, 222, 116, 177, 4, 209, 34, 160, 57, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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