← previous blocknext block →recent activity
Analyzing
Block #87,905,218
14 transactions · 13 stateful · 2026-07-15 11:21:59 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,905,218 · 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
1w02w16w08w09w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30f3ece3…c237
0x34b655…2a6f
4 touches
1 conflict
0xfd03527f…d840
0x34b655…2a6f
4 touches
1 conflict
0xc577f898…dd33
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7d7ff6bb…f729
0x34b655…2a6f
4 touches
1 conflict
0xf77ff27d…3c41
0xd32edf…ff58
3 touches
1 conflict
0xba5743c7…21c0
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 0x30f3ece315…53c237
Audit this contract →
← previous block·next block →recent activity