← previous blocknext block →recent activity
Analyzing
Block #88,806,914
14 transactions · 14 stateful · 2026-07-19 15:54:58 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,806,914 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x25ff7717…d4af
0x34b655…2a6f
4 touches
1 conflict
0x4d881056…0d39
0x34b655…2a6f
4 touches
1 conflict
0x90fefe5e…f0c6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xb7c8652f…ebce
0x1111b3…4111
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity