← previous blocknext block →recent activity
Analyzing
Block #87,623,943
18 transactions · 18 stateful · 2026-07-14 04:00:35 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,623,943 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w29w310w412w515w216w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x588c5b6a…60d2
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
6 touches
3 conflicts
0x6638e124…bc7f
0x34b655…2a6f
6 touches
3 conflicts
0x80bf58f2…be95
0x34b655…2a6f
6 touches
3 conflicts
0x80bf58f2…be96
0x34b655…2a6f
6 touches
3 conflicts
0x9aa29e0c…eb5b
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x588c5b6adb…3060d2
Audit this contract →
← previous block·next block →recent activity