Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f82664bd7a2a4b8d16095363f099cf36845fb13cdc2080ad6a6bb6c73bb8986e

Tx prefix hash: fc94bdac0ab30a3c04210dd97b1a07bb660aab1c8c08a80f81f0944415403334
Tx public key: da3ab385422503afdcb96dd5e0e89dcf9a38c316a032f21a33c9b733afe19396
Timestamp: 1714579763 Timestamp [UCT]: 2024-05-01 16:09:23 Age [y:d:h:m:s]: 00:346:04:27:53
Block: 1012618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247469 RingCT/type: yes/0
Extra: 01da3ab385422503afdcb96dd5e0e89dcf9a38c316a032f21a33c9b733afe193960211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bbe5c7b3a847f0dc3a30efd3667bbfafecb0085cd43aedbbe830726bda28149 0.600000000000 1475202 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": 1012628, "vin": [ { "gen": { "height": 1012618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bbe5c7b3a847f0dc3a30efd3667bbfafecb0085cd43aedbbe830726bda28149" } } ], "extra": [ 1, 218, 58, 179, 133, 66, 37, 3, 175, 220, 185, 109, 213, 224, 232, 157, 207, 154, 56, 195, 22, 160, 50, 242, 26, 51, 201, 183, 51, 175, 225, 147, 150, 2, 17, 0, 0, 0, 2, 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