Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13f0957c737bb384e5a4755e9d53d98c605732c33c3564c8b8c9c5981327dff4

Tx prefix hash: b16a6507fe905d5909f6c8e47d25c4fdabccccfa37976c32bcc7e5540cbec1ec
Tx public key: de2f6ff453013953df502beb4ceb866b5d708c36703669a3b23353d371262e8c
Timestamp: 1712182711 Timestamp [UCT]: 2024-04-03 22:18:31 Age [y:d:h:m:s]: 00:241:11:01:55
Block: 992716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172896 RingCT/type: yes/0
Extra: 01de2f6ff453013953df502beb4ceb866b5d708c36703669a3b23353d371262e8c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6be3d073294be44ae20f22ead9edc92c599e51627ec6a1dd6f3d01c0f4f9652 0.600000000000 1453090 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": 992726, "vin": [ { "gen": { "height": 992716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6be3d073294be44ae20f22ead9edc92c599e51627ec6a1dd6f3d01c0f4f9652" } } ], "extra": [ 1, 222, 47, 111, 244, 83, 1, 57, 83, 223, 80, 43, 235, 76, 235, 134, 107, 93, 112, 140, 54, 112, 54, 105, 163, 178, 51, 83, 211, 113, 38, 46, 140, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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