← previous blocknext block →recent activity
Analyzing
Block #87,611,488
15 transactions · 14 stateful · 2026-07-14 02:37:18 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,611,488 · 15 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
3w05w16w210w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd50d8366…df9c
0x34b655…2a6f
4 touches
1 conflict
0xd50d8366…df9d
0x34b655…2a6f
4 touches
1 conflict
0xf2f40f08…5cdb
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x745952b2…d90c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb05cd4f5…73d0
0x2b46c0…1669
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 0xd50d836695…72df9c
Audit this contract →
← previous block·next block →recent activity