Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38e1cbed3c4f61c629cfa2764116c44fc7f6739cf6d11b0229064aa6dc357203

Tx prefix hash: 918c8a9f6388b2823ffc15bf5268cad93e6a19298379bbc484d77f8f344d5195
Tx public key: 7da0dafec80dbf50fc73f5a0ae77ad995e3ae99ced816b1ab98c3919a2f4fe39
Timestamp: 1713146151 Timestamp [UCT]: 2024-04-15 01:55:51 Age [y:d:h:m:s]: 01:018:16:20:35
Block: 1000711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274326 RingCT/type: yes/0
Extra: 017da0dafec80dbf50fc73f5a0ae77ad995e3ae99ced816b1ab98c3919a2f4fe390211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1f3a096751401c1550e8ff8c08db20d51239d4a7ec74933dfb7786766cc5034 0.600000000000 1461209 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": 1000721, "vin": [ { "gen": { "height": 1000711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1f3a096751401c1550e8ff8c08db20d51239d4a7ec74933dfb7786766cc5034" } } ], "extra": [ 1, 125, 160, 218, 254, 200, 13, 191, 80, 252, 115, 245, 160, 174, 119, 173, 153, 94, 58, 233, 156, 237, 129, 107, 26, 185, 140, 57, 25, 162, 244, 254, 57, 2, 17, 0, 0, 0, 4, 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