Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3af8f7d64f346763883898c0df322de5daeb5fbd6c5e676ab46134a5e9d09d12

Tx prefix hash: 4765734e86e1ce59e51285f5b65694322d9ee3aadb633127e845e82589f9b3d9
Tx public key: e32848c14bb889a8a158d3e603eb0b0c403f17a3caf2317ad04a25b6f298ab0c
Timestamp: 1727839584 Timestamp [UCT]: 2024-10-02 03:26:24 Age [y:d:h:m:s]: 00:053:00:58:14
Block: 1122556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37888 RingCT/type: yes/0
Extra: 01e32848c14bb889a8a158d3e603eb0b0c403f17a3caf2317ad04a25b6f298ab0c021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b0951e7775eb578303fcbb6da2ab4d2b65d91a764e256133bdcc0c8a752f281 0.600000000000 1605025 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": 1122566, "vin": [ { "gen": { "height": 1122556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b0951e7775eb578303fcbb6da2ab4d2b65d91a764e256133bdcc0c8a752f281" } } ], "extra": [ 1, 227, 40, 72, 193, 75, 184, 137, 168, 161, 88, 211, 230, 3, 235, 11, 12, 64, 63, 23, 163, 202, 242, 49, 122, 208, 74, 37, 182, 242, 152, 171, 12, 2, 17, 0, 0, 0, 5, 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