← previous blocknext block →recent activity
Analyzing
Block #96,508,195
11 transactions · 11 stateful · 2026-08-16 14:01:08 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,508,195 · 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
1w02w17w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4188cc5f…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x0460135c…98fd
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0x19439a65…eb51
0x34b655…2a6f
2 touches
0 conflicts
0x2acdf73b…fbae
0x34b655…2a6f
2 touches
0 conflicts
0x2ad2e6d1…e192
0x34b655…2a6f
2 touches
0 conflicts
0x45b57036…844b
0x34b655…2a6f
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 0x4188cc5f13…782d2e
Audit this contract →
← previous block·next block →recent activity