Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae8ab40cc3a5ace6d69742768b6169a646e1cbd327f929a1699a6955e829b87e

Tx prefix hash: d40d1cbf9e63966a000bf10cacd9a3bf98d203d6ca116f5c22fc3d509f7b0b04
Tx public key: 628cc1ece72b105e1c59aff66d1a6ce5317bc4675b9643294195fb2a266a26d6
Timestamp: 1709235479 Timestamp [UCT]: 2024-02-29 19:37:59 Age [y:d:h:m:s]: 01:061:09:47:41
Block: 968319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304897 RingCT/type: yes/0
Extra: 01628cc1ece72b105e1c59aff66d1a6ce5317bc4675b9643294195fb2a266a26d602110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3358aa8ea2ba81054d07ad3e251be408fd754cc932b59e3182ef70f03a4ad659 0.600000000000 1428128 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": 968329, "vin": [ { "gen": { "height": 968319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3358aa8ea2ba81054d07ad3e251be408fd754cc932b59e3182ef70f03a4ad659" } } ], "extra": [ 1, 98, 140, 193, 236, 231, 43, 16, 94, 28, 89, 175, 246, 109, 26, 108, 229, 49, 123, 196, 103, 91, 150, 67, 41, 65, 149, 251, 42, 38, 106, 38, 214, 2, 17, 0, 0, 0, 4, 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