Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00c1a64e529e1c7d0cb04d912a2b8c7def153242aa23b1c53389867b45a8fd7f

Tx prefix hash: 6f1514ecf0afaff5737aa32ecabc8524cdd4c7a0de2ac2f3d09819a9114561b6
Tx public key: 09cd34b0fac62de9ca8595e5ecdf0f1a2744fa2763ffa1bf904726cd45b6e3fb
Timestamp: 1657020067 Timestamp [UCT]: 2022-07-05 11:21:07 Age [y:d:h:m:s]: 02:259:03:12:04
Block: 537120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 706368 RingCT/type: yes/0
Extra: 0109cd34b0fac62de9ca8595e5ecdf0f1a2744fa2763ffa1bf904726cd45b6e3fb0211000000124da16a3a000000000000000000

1 output(s) for total of 10.192920150000 dcy

stealth address amount amount idx
00: 41f28ed6fdc31de2b4b6f04a050b34c582bfaa5b3177742fb5e4a72f46b506ac 10.192920150000 966977 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": 537130, "vin": [ { "gen": { "height": 537120 } } ], "vout": [ { "amount": 10192920150, "target": { "key": "41f28ed6fdc31de2b4b6f04a050b34c582bfaa5b3177742fb5e4a72f46b506ac" } } ], "extra": [ 1, 9, 205, 52, 176, 250, 198, 45, 233, 202, 133, 149, 229, 236, 223, 15, 26, 39, 68, 250, 39, 99, 255, 161, 191, 144, 71, 38, 205, 69, 182, 227, 251, 2, 17, 0, 0, 0, 18, 77, 161, 106, 58, 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