Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41c0b1e7cbc000cbf0b5023e882d2af102feb14235e03e6b1e1098c77419a259

Tx prefix hash: cf1e846f7b5bf378f7f081f86272b027fde6c9caf824969eb63907e135da3ba1
Tx public key: 41986621379a9e6017450d53a5065088c118ae99841425c21883b397c9652480
Timestamp: 1705465169 Timestamp [UCT]: 2024-01-17 04:19:29 Age [y:d:h:m:s]: 00:360:03:41:00
Block: 937025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257867 RingCT/type: yes/0
Extra: 0141986621379a9e6017450d53a5065088c118ae99841425c21883b397c96524800211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b4f9b34e3fd4e5c0cfe36b518be2eb3e1272501703a089011f64da6f6f3a917 0.600000000000 1395069 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": 937035, "vin": [ { "gen": { "height": 937025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b4f9b34e3fd4e5c0cfe36b518be2eb3e1272501703a089011f64da6f6f3a917" } } ], "extra": [ 1, 65, 152, 102, 33, 55, 154, 158, 96, 23, 69, 13, 83, 165, 6, 80, 136, 193, 24, 174, 153, 132, 20, 37, 194, 24, 131, 179, 151, 201, 101, 36, 128, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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