Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35b6643b269827459a10c24c64eefbe1d2e820b96dc2cd1f85318b50658c385e

Tx prefix hash: 22fe796bd68097aa2bbdb39b25981bb89a0d43cecf25c17d9a0411a958f7aff7
Tx public key: 0f82f823f08d2cd6f71b7c0ac9e27e152d65b8a7a79e27f7c55393ed67d6a5ab
Timestamp: 1734407053 Timestamp [UCT]: 2024-12-17 03:44:13 Age [y:d:h:m:s]: 01:004:18:02:59
Block: 1176905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261805 RingCT/type: yes/0
Extra: 010f82f823f08d2cd6f71b7c0ac9e27e152d65b8a7a79e27f7c55393ed67d6a5ab0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2770a099200f03ab57e8a5d49a04c2fb24e38b7dbcb84dabfb5779f15b6f35d 0.600000000000 1663266 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": 1176915, "vin": [ { "gen": { "height": 1176905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2770a099200f03ab57e8a5d49a04c2fb24e38b7dbcb84dabfb5779f15b6f35d" } } ], "extra": [ 1, 15, 130, 248, 35, 240, 141, 44, 214, 247, 27, 124, 10, 201, 226, 126, 21, 45, 101, 184, 167, 167, 158, 39, 247, 197, 83, 147, 237, 103, 214, 165, 171, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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