Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75be2c74539ce445e30d486fb991c705d4c0736e74cd839ed62e925af0f41ba3

Tx prefix hash: c9fc5298e19bf719a12dcc6f62f5c92542ed0aea4564797b81525ac17a5b58a4
Tx public key: db7de9b713cfe05935793195caacd6a216075ecb1cc9f1fef52484019b022675
Timestamp: 1706176077 Timestamp [UCT]: 2024-01-25 09:47:57 Age [y:d:h:m:s]: 01:134:18:50:43
Block: 942923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357470 RingCT/type: yes/0
Extra: 01db7de9b713cfe05935793195caacd6a216075ecb1cc9f1fef52484019b02267502110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7039a66afdf1d4e860acb07e293d127381d03a020d1388e7b8163e2070f2da0 0.600000000000 1401103 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": 942933, "vin": [ { "gen": { "height": 942923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7039a66afdf1d4e860acb07e293d127381d03a020d1388e7b8163e2070f2da0" } } ], "extra": [ 1, 219, 125, 233, 183, 19, 207, 224, 89, 53, 121, 49, 149, 202, 172, 214, 162, 22, 7, 94, 203, 28, 201, 241, 254, 245, 36, 132, 1, 155, 2, 38, 117, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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