Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53c95f656e8c43cd7e656dfc0913f959d0cef0204c276bb8e8d9fedf7109c02e

Tx prefix hash: 8aed5bdea0ffce0385a176b13bfca9f12fbf4b638ebc306f2deebcf615414e7e
Tx public key: baa3ff609d5dcf9f2889eaf156fd48ead08e36878c0adda0a7a645541ddfb71a
Timestamp: 1710384601 Timestamp [UCT]: 2024-03-14 02:50:01 Age [y:d:h:m:s]: 01:095:04:53:58
Block: 977855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328950 RingCT/type: yes/0
Extra: 01baa3ff609d5dcf9f2889eaf156fd48ead08e36878c0adda0a7a645541ddfb71a0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d37ee70d53e986c97b7d52fd64583cc4f63a61b0594534f00aea52b16f4e3fb8 0.600000000000 1437862 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": 977865, "vin": [ { "gen": { "height": 977855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d37ee70d53e986c97b7d52fd64583cc4f63a61b0594534f00aea52b16f4e3fb8" } } ], "extra": [ 1, 186, 163, 255, 96, 157, 93, 207, 159, 40, 137, 234, 241, 86, 253, 72, 234, 208, 142, 54, 135, 140, 10, 221, 160, 167, 166, 69, 84, 29, 223, 183, 26, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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