Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8cea8b06c30d35767f1cd4165dae461c2fded4899ed77ab443bfb4875364cf4

Tx prefix hash: 96bf3bf8c1edf3e08ae09a54d5a4d3ca510ee2eee86cab246e825499246bc426
Tx public key: 4ec48b2ef04c790b5942b8a8b568ccbc89c02443cef45fe7cfd9bb5adc92cb5c
Timestamp: 1728088361 Timestamp [UCT]: 2024-10-05 00:32:41 Age [y:d:h:m:s]: 00:252:18:34:28
Block: 1124609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180422 RingCT/type: yes/0
Extra: 014ec48b2ef04c790b5942b8a8b568ccbc89c02443cef45fe7cfd9bb5adc92cb5c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a674d177b7ba1fead7e3f8c30f66be49553eeb8eef2d38e95e59e9a30ad6ae51 0.600000000000 1607258 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": 1124619, "vin": [ { "gen": { "height": 1124609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a674d177b7ba1fead7e3f8c30f66be49553eeb8eef2d38e95e59e9a30ad6ae51" } } ], "extra": [ 1, 78, 196, 139, 46, 240, 76, 121, 11, 89, 66, 184, 168, 181, 104, 204, 188, 137, 192, 36, 67, 206, 244, 95, 231, 207, 217, 187, 90, 220, 146, 203, 92, 2, 17, 0, 0, 0, 3, 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