Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c42d74a4a64835c3ecfb0ee8dded1758c0ce779ff6b3aba81ee92605117eb74

Tx prefix hash: c68e8fe3c14ba1e86aed54870107468b8897a4c1d0350cbdb5d72bb742d6048d
Tx public key: c957420ee6e039a1435f75e4aa5767cdbdb9d16d10a3209630fc602c96b3d60d
Timestamp: 1738563359 Timestamp [UCT]: 2025-02-03 06:15:59 Age [y:d:h:m:s]: 00:363:04:10:50
Block: 1211012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257253 RingCT/type: yes/0
Extra: 01c957420ee6e039a1435f75e4aa5767cdbdb9d16d10a3209630fc602c96b3d60d0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a32fe0c5eeff40955f60fe635d7c0ae1a6e84bc07f21ef7a81cf9b1ee5564f3c 0.600000000000 1697767 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": 1211022, "vin": [ { "gen": { "height": 1211012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a32fe0c5eeff40955f60fe635d7c0ae1a6e84bc07f21ef7a81cf9b1ee5564f3c" } } ], "extra": [ 1, 201, 87, 66, 14, 230, 224, 57, 161, 67, 95, 117, 228, 170, 87, 103, 205, 189, 185, 209, 109, 16, 163, 32, 150, 48, 252, 96, 44, 150, 179, 214, 13, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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