Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31b9ab536809b7ff7bcb3b3cf53d9c9a7386416c1954f9e58f7db5a2842bed46

Tx prefix hash: 491064d2e6f5e3f61d649a1900b0f8b1bebfe852e280c797f9808026e097c446
Tx public key: 39f3dace7375472b67bc147d8cd382c8a9f081c3b4f0dd45d337513addff81ee
Timestamp: 1724113345 Timestamp [UCT]: 2024-08-20 00:22:25 Age [y:d:h:m:s]: 00:226:18:11:49
Block: 1091664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161916 RingCT/type: yes/0
Extra: 0139f3dace7375472b67bc147d8cd382c8a9f081c3b4f0dd45d337513addff81ee021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5836ff371f7016c06e094eb55ebf8736c892cd241f3469618a892fafe0a6420 0.600000000000 1566297 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": 1091674, "vin": [ { "gen": { "height": 1091664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5836ff371f7016c06e094eb55ebf8736c892cd241f3469618a892fafe0a6420" } } ], "extra": [ 1, 57, 243, 218, 206, 115, 117, 71, 43, 103, 188, 20, 125, 140, 211, 130, 200, 169, 240, 129, 195, 180, 240, 221, 69, 211, 55, 81, 58, 221, 255, 129, 238, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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