← previous blocknext block →recent activity
Analyzing
Block #87,716,203
23 transactions · 19 stateful · 2026-07-14 14:17:38 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,716,203 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w110w211w315w116w217w419w121w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd36917c…b88b
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x7c7eff13…16db
0x34b655…2a6f
4 touches
1 conflict
0x7eb90864…574d
0x34b655…2a6f
4 touches
1 conflict
0x85c84f98…06d7
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x93b6fab0…09d6
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 0xdd36917cc2…d4b88b
Audit this contract →
← previous block·next block →recent activity