← previous blocknext block →recent activity
Analyzing
Block #96,795,495
22 transactions · 21 stateful · 2026-08-17 14:06:07 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,795,495 · 22 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
1w02w03w14w05w07w18w29w010w113w214w315w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35d
0x34b655…2a6f
10 touches
10 conflicts
0xc5a1b2fe…5369
0x34b655…2a6f
10 touches
10 conflicts
0xcd26fba5…21c6
0x34b655…2a6f
10 touches
10 conflicts
0x46e9575c…6fa1
0x34b655…2a6f
9 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x523de645…4f58
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x261cbea79d…12e35d
Audit this contract →
← previous block·next block →recent activity