Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0779f254421ab485fae2b74a1c9915c92fc3abb7b6c3ff1fb9165d020ff614a6

Tx prefix hash: 82330c2453bc7af8e84454ac525b914f4aed5b20c94b66544bd80a2baed1d0d9
Tx public key: 7a80a13cb65eb7446155430b11a52928608a737f4405f20eb3c5046f286b212b
Timestamp: 1694837027 Timestamp [UCT]: 2023-09-16 04:03:47 Age [y:d:h:m:s]: 01:202:07:14:32
Block: 849126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405678 RingCT/type: yes/0
Extra: 017a80a13cb65eb7446155430b11a52928608a737f4405f20eb3c5046f286b212b021100000007faf35c9c000000000000000000

1 output(s) for total of 0.942959697000 dcy

stealth address amount amount idx
00: 4f915ede7aca5ef598d791f106e5f23ea41d9024cc38e88bf0b17afbff30f045 0.942959697000 1302770 of 0

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": 849136, "vin": [ { "gen": { "height": 849126 } } ], "vout": [ { "amount": 942959697, "target": { "key": "4f915ede7aca5ef598d791f106e5f23ea41d9024cc38e88bf0b17afbff30f045" } } ], "extra": [ 1, 122, 128, 161, 60, 182, 94, 183, 68, 97, 85, 67, 11, 17, 165, 41, 40, 96, 138, 115, 127, 68, 5, 242, 14, 179, 197, 4, 111, 40, 107, 33, 43, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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