Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 834f3c13bfa50d99ae6a39f1f702ed932356825feead3dae0ad598ca983d3474

Tx prefix hash: 186dde2d799d3be5d37e96caaffefcc93c26fa357549612e42223e015e5c9303
Tx public key: 92274cef640adb70fd74ee1635333df084a2d6375c1d5e6cfe8555553174a40c
Timestamp: 1708143390 Timestamp [UCT]: 2024-02-17 04:16:30 Age [y:d:h:m:s]: 01:040:13:16:38
Block: 959253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290018 RingCT/type: yes/0
Extra: 0192274cef640adb70fd74ee1635333df084a2d6375c1d5e6cfe8555553174a40c021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c0f058e63aea827bd8f77282367136c7d745ba2a802dc6fb8d1c82e2d0c5992 0.600000000000 1418784 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": 959263, "vin": [ { "gen": { "height": 959253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c0f058e63aea827bd8f77282367136c7d745ba2a802dc6fb8d1c82e2d0c5992" } } ], "extra": [ 1, 146, 39, 76, 239, 100, 10, 219, 112, 253, 116, 238, 22, 53, 51, 61, 240, 132, 162, 214, 55, 92, 29, 94, 108, 254, 133, 85, 85, 49, 116, 164, 12, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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