Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a77a9d2187785b34191db1d6d66101b7cbd5a411a8e732364a3b21efc280aa83

Tx prefix hash: ab1ac437a03949df277dd907af64c3e3501c40c581915a1215a143596d666925
Tx public key: 206fa975661c5c5c772b8dd6b13d66f15d0e0b19908080f4362c95bbf181d652
Timestamp: 1682358938 Timestamp [UCT]: 2023-04-24 17:55:38 Age [y:d:h:m:s]: 01:274:15:49:00
Block: 745740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457737 RingCT/type: yes/0
Extra: 01206fa975661c5c5c772b8dd6b13d66f15d0e0b19908080f4362c95bbf181d65202110000000275e3f0e9000000000000000000

1 output(s) for total of 2.075171613000 dcy

stealth address amount amount idx
00: 84ab9bcc4f58bfcc14903bab3cc2a808caf75ec7a400bbeacb37d1e12f4c810a 2.075171613000 1193219 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": 745750, "vin": [ { "gen": { "height": 745740 } } ], "vout": [ { "amount": 2075171613, "target": { "key": "84ab9bcc4f58bfcc14903bab3cc2a808caf75ec7a400bbeacb37d1e12f4c810a" } } ], "extra": [ 1, 32, 111, 169, 117, 102, 28, 92, 92, 119, 43, 141, 214, 177, 61, 102, 241, 93, 14, 11, 25, 144, 128, 128, 244, 54, 44, 149, 187, 241, 129, 214, 82, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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