← previous blocknext block →recent activity
Analyzing
Block #88,085,889
14 transactions · 12 stateful · 2026-07-16 07:30:24 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,085,889 · 14 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
8w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x266a6b2c…4377
0x34b655…2a6f
4 touches
1 conflict
0xa524a39b…df24
0x34b655…2a6f
4 touches
1 conflict
0xe3ab3114…678a
0x34b655…2a6f
4 touches
1 conflict
0x266a6b2c…4376
0x34b655…2a6f
4 touches
1 conflict
0x81ec12ed…a506
0x34b655…2a6f
3 touches
1 conflict
0x44b2e7c9…4de0
0x34b655…2a6f
3 touches
1 conflict
0x9665c389…06fb
0x34b655…2a6f
3 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
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 0x266a6b2c33…a14377
Audit this contract →
← previous block·next block →recent activity