← previous blocknext block →recent activity
Analyzing
Block #95,782,100
20 transactions · 18 stateful · 2026-08-14 01:08:16 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,782,100 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w28w39w413w114w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x4efae872…6aa8
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xf9444acb…193d
0x34b655…2a6f
8 touches
6 conflicts
0xcb674fb5…9393
0x34b655…2a6f
8 touches
6 conflicts
0xf76df566…dffd
0x34b655…2a6f
7 touches
6 conflicts
0x5b6af007…0f35
0x34b655…2a6f
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity