← previous blocknext block →recent activity
Analyzing
Block #87,910,633
13 transactions · 8 stateful · 2026-07-15 11:58:13 UTC
Parallelism
62/100
Blocked
63%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,910,633 · 13 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
5w06w18w29w310w412w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa013ecc1…7c8f
0x34b655…2a6f
6 touches
3 conflicts
0x2000b734…5e5a
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x1a6cdc0e…0af5
0x34b655…2a6f
4 touches
1 conflict
0x30ab53da…3529
0x34b655…2a6f
4 touches
1 conflict
0x51491cb1…0207
0x34b655…2a6f
4 touches
1 conflict
0x51491cb1…0208
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0xa013ecc17b…017c8f
Audit this contract →
← previous block·next block →recent activity