← previous blocknext block →recent activity
Analyzing
Block #88,088,510
16 transactions · 14 stateful · 2026-07-16 07:47:55 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,088,510 · 16 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
6w07w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35b89cd8…5092
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x2b96adb2…ba5d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x27b9caf2…c102
0x34b655…2a6f
2 touches
0 conflicts
0x4ae1e116…4249
0x34b655…2a6f
2 touches
0 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
2 touches
0 conflicts
0x823a3658…acf6
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 0x35b89cd80c…f05092
Audit this contract →
← previous block·next block →recent activity