Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f96e77e85285c7a9d068aa62911efd9796817ab9c7327587c9aad24a290eebdc

Tx prefix hash: 2b67bd7a6d2b82f1296c298c441bd358b5592232af72e4a1261f66c94dae0b73
Tx public key: 3dd4da5c8da5a8decce103f6c72869548b97dc268e78b6ea2b953100c6e22302
Timestamp: 1722361594 Timestamp [UCT]: 2024-07-30 17:46:34 Age [y:d:h:m:s]: 00:325:16:18:28
Block: 1077130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232549 RingCT/type: yes/0
Extra: 013dd4da5c8da5a8decce103f6c72869548b97dc268e78b6ea2b953100c6e2230202110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: beed433d264454cac7a881fec8fc1cf9b5677a4fae6eace32dc9e967fbe9f7ed 0.600000000000 1549675 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": 1077140, "vin": [ { "gen": { "height": 1077130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "beed433d264454cac7a881fec8fc1cf9b5677a4fae6eace32dc9e967fbe9f7ed" } } ], "extra": [ 1, 61, 212, 218, 92, 141, 165, 168, 222, 204, 225, 3, 246, 199, 40, 105, 84, 139, 151, 220, 38, 142, 120, 182, 234, 43, 149, 49, 0, 198, 226, 35, 2, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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