← previous blocknext block →recent activity
Analyzing
Block #87,166,193
18 transactions · 18 stateful · 2026-07-12 00:57:49 UTC
Parallelism
72/100
Blocked
28%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,166,193 · 18 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
1w05w09w110w211w113w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0446875…2b96
0x34b655…2a6f
6 touches
3 conflicts
0xb2343b3d…9905
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x2e177343…2f8c
0x34b655…2a6f
4 touches
1 conflict
0xa84ca715…9c73
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x43ffd8bd…0d0c
0x34b655…2a6f
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
3 conflicts on slot 0xb04468752d…352b96
Audit this contract →
← previous block·next block →recent activity