← previous blocknext block →recent activity
Analyzing
Block #87,903,223
18 transactions · 17 stateful · 2026-07-15 11:08:40 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,903,223 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w19w010w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe45167d0…c16c
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x96bfa04d…d06b
0x34b655…2a6f
6 touches
3 conflicts
0x3f7d8a09…362c
0x34b655…2a6f
4 touches
1 conflict
0x41d9a134…ccfe
0x34b655…2a6f
4 touches
1 conflict
0x4ce41dcc…e297
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
0x34b655…2a6f
4 touches
1 conflict
0x5aed1bd2…7afa
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xe45167d0d8…c2c16c
Audit this contract →
← previous block·next block →recent activity