← previous blocknext block →recent activity
Analyzing
Block #96,276,085
11 transactions · 6 stateful · 2026-08-15 18:33:25 UTC
Parallelism
82/100
Blocked
17%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,276,085 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67a56c8b…f955
0x34b655…2a6f
4 touches
1 conflict
0x70be0d05…fc4e
0x34b655…2a6f
4 touches
1 conflict
0x8ec95f2b…f4d7
0x34b655…2a6f
4 touches
1 conflict
0x9a8b7004…3e0a
0x34b655…2a6f
4 touches
1 conflict
0x9fc52439…5214
0x0a4fcb…a602
2 touches
0 conflicts
0x9fc52439…5215
0x0a4fcb…a602
2 touches
0 conflicts
0x9fc52439…5217
0x0a4fcb…a602
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 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
1 conflict on slot 0x67a56c8b2e…d7f955
Audit this contract →
← previous block·next block →recent activity