← previous blocknext block →recent activity
Analyzing
Block #87,489,749
23 transactions · 21 stateful · 2026-07-13 13:02:18 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,489,749 · 23 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
1w04w06w07w18w29w010w112w213w315w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4ab
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xf1e0de4d…eb7f
0x34b655…2a6f
6 touches
3 conflicts
0x5d1f2b49…7b0a
0x34b655…2a6f
6 touches
3 conflicts
0xc2099fec…321d
0x34b655…2a6f
6 touches
3 conflicts
0x727fbce7…0c80
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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 0x7e5ea60ab2…b0c4ab
Audit this contract →
← previous block·next block →recent activity