Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36f5d68d3bcfe60e483b1effc5103c2e82c16a78993ffffc1da46f038796fb5f

Tx prefix hash: fe4dae7c5f35689cd74242788145760e20be14b7969e1b47ba974f5d415fad22
Tx public key: 4f57e9f0011b1c733bb3307b1f53725ad02a8d70a8e6bff3dec7ecda7a46c161
Timestamp: 1710312601 Timestamp [UCT]: 2024-03-13 06:50:01 Age [y:d:h:m:s]: 01:064:16:34:54
Block: 977251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307237 RingCT/type: yes/0
Extra: 014f57e9f0011b1c733bb3307b1f53725ad02a8d70a8e6bff3dec7ecda7a46c16102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2755c20c83e9454004a6b3ab4036ded2d91885bc5781bafb54c2858f5a4cf6dd 0.600000000000 1437252 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": 977261, "vin": [ { "gen": { "height": 977251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2755c20c83e9454004a6b3ab4036ded2d91885bc5781bafb54c2858f5a4cf6dd" } } ], "extra": [ 1, 79, 87, 233, 240, 1, 27, 28, 115, 59, 179, 48, 123, 31, 83, 114, 90, 208, 42, 141, 112, 168, 230, 191, 243, 222, 199, 236, 218, 122, 70, 193, 97, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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