Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b064f6f5f73da197debf5fff7523a1a6870245c175d5d7b4340575cb4ef6186

Tx prefix hash: d104cca55b5df47fd9af64f70c26f6d53dc4dec160a2eb1bce73106e417d25d8
Tx public key: 1d84e1a2d0167c89d0fd04e3b4d1c33b4902abfcd82a10e54b935540709c7441
Timestamp: 1743960904 Timestamp [UCT]: 2025-04-06 17:35:04 Age [y:d:h:m:s]: 00:184:08:02:37
Block: 1255694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129424 RingCT/type: yes/0
Extra: 011d84e1a2d0167c89d0fd04e3b4d1c33b4902abfcd82a10e54b935540709c74410211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e7b48c935da17834630102c3f5cc0da08b8c5a4a528aa48f99f51240767472c 0.600000000000 1742799 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": 1255704, "vin": [ { "gen": { "height": 1255694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e7b48c935da17834630102c3f5cc0da08b8c5a4a528aa48f99f51240767472c" } } ], "extra": [ 1, 29, 132, 225, 162, 208, 22, 124, 137, 208, 253, 4, 227, 180, 209, 195, 59, 73, 2, 171, 252, 216, 42, 16, 229, 75, 147, 85, 64, 112, 156, 116, 65, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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