Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0511d73f5198a8dfb9ca0dbe295f12da3e5c413b86956a758030a4fd73e4a07

Tx prefix hash: 7cc2f60ef6ebc43379bfde0ce11417b2bcc6142c6397549f68b37d74a21dfea9
Tx public key: c2524121a217eafca5a244fc88b13535de52763adc6d96a4a55a5475e940502a
Timestamp: 1675505099 Timestamp [UCT]: 2023-02-04 10:04:59 Age [y:d:h:m:s]: 01:343:08:31:21
Block: 689554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506368 RingCT/type: yes/0
Extra: 01c2524121a217eafca5a244fc88b13535de52763adc6d96a4a55a5475e940502a0211000000015029cbac000000000000000000

1 output(s) for total of 3.185820328000 dcy

stealth address amount amount idx
00: e2d702dfd649f5b6950d1c82d9802a55a825b127cb41d5a8645642f357f579ee 3.185820328000 1132238 of 0

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": 689564, "vin": [ { "gen": { "height": 689554 } } ], "vout": [ { "amount": 3185820328, "target": { "key": "e2d702dfd649f5b6950d1c82d9802a55a825b127cb41d5a8645642f357f579ee" } } ], "extra": [ 1, 194, 82, 65, 33, 162, 23, 234, 252, 165, 162, 68, 252, 136, 177, 53, 53, 222, 82, 118, 58, 220, 109, 150, 164, 165, 90, 84, 117, 233, 64, 80, 42, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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