Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2dbf9e7b80679bc6f282806ac2d6438a43e6dc6f261ca2be5985fb0f34259b2

Tx prefix hash: 71e83aba15fb3f4c5198dc15de5983899c7d3f83b99a8717f760f8977e460ce5
Tx public key: 0c9c18532150540641fe9c51077636224765b426923d6f84e6e457e0a0be8b97
Timestamp: 1713063292 Timestamp [UCT]: 2024-04-14 02:54:52 Age [y:d:h:m:s]: 00:200:12:35:53
Block: 1000024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143579 RingCT/type: yes/0
Extra: 010c9c18532150540641fe9c51077636224765b426923d6f84e6e457e0a0be8b970211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ebe6817e839e1d6ef7a7c6a4f3ddedf78317ef7d92928c8877dbda37116d946 0.600000000000 1460514 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": 1000034, "vin": [ { "gen": { "height": 1000024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ebe6817e839e1d6ef7a7c6a4f3ddedf78317ef7d92928c8877dbda37116d946" } } ], "extra": [ 1, 12, 156, 24, 83, 33, 80, 84, 6, 65, 254, 156, 81, 7, 118, 54, 34, 71, 101, 180, 38, 146, 61, 111, 132, 230, 228, 87, 224, 160, 190, 139, 151, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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