← previous blocknext block →recent activity
Analyzing
Block #87,718,218
22 transactions · 22 stateful · 2026-07-14 14:31:11 UTC
Parallelism
82/100
Blocked
36%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,718,218 · 22 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
1w02w14w05w110w211w113w214w317w219w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f234b05…db39
0x34b655…2a6f
6 touches
3 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x270fa94a…95a6
0x34b655…2a6f
4 touches
1 conflict
0x3674075e…02b7
0x34b655…2a6f
4 touches
1 conflict
0x5abca0c6…2323
0x34b655…2a6f
4 touches
1 conflict
0x5b77c7c4…59b0
0x34b655…2a6f
4 touches
1 conflict
0x5bf44783…6166
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 0x5f234b05a2…82db39
Audit this contract →
← previous block·next block →recent activity