Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8d886699c2fc1bf79567e93e2f9bb3c6a595bab13d55c2cb5ddab7e2918093d

Tx prefix hash: c23c11e0ae8c5f843cd28e203eb59a306bf402d400cd5824439a29e0df95111b
Tx public key: ee4239fdd950043358c2d5267930cc34b0379551cdedf3f4df347f91d296a05a
Timestamp: 1705875552 Timestamp [UCT]: 2024-01-21 22:19:12 Age [y:d:h:m:s]: 01:107:08:49:54
Block: 940428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337855 RingCT/type: yes/0
Extra: 01ee4239fdd950043358c2d5267930cc34b0379551cdedf3f4df347f91d296a05a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa21acf0162d6008ce8d471636fb81df5c86df8e5357f3c1d5fd9fbfc353f78a 0.600000000000 1398566 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": 940438, "vin": [ { "gen": { "height": 940428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa21acf0162d6008ce8d471636fb81df5c86df8e5357f3c1d5fd9fbfc353f78a" } } ], "extra": [ 1, 238, 66, 57, 253, 217, 80, 4, 51, 88, 194, 213, 38, 121, 48, 204, 52, 176, 55, 149, 81, 205, 237, 243, 244, 223, 52, 127, 145, 210, 150, 160, 90, 2, 17, 0, 0, 0, 2, 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