← previous blocknext block →recent activity
Analyzing
Block #87,785,149
19 transactions · 16 stateful · 2026-07-14 21:58:55 UTC
Parallelism
74/100
Blocked
44%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,785,149 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w09w110w212w313w414w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x9001f549…089d
0x34b655…2a6f
6 touches
3 conflicts
0x428b6e5b…8909
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x69b3f686…a717
0x34b655…2a6f
4 touches
1 conflict
0x7ea5ce4b…1e5b
0x34b655…2a6f
4 touches
1 conflict
0x9ae859db…2d84
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity