← previous blocknext block →recent activity
Analyzing
Block #87,487,343
13 transactions · 12 stateful · 2026-07-13 12:46:11 UTC
Parallelism
54/100
Blocked
50%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,487,343 · 13 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
2w03w16w17w28w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x5cacfb02…ef32
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
8 touches
6 conflicts
0x1a6cdc0e…0af5
0x34b655…2a6f
6 touches
3 conflicts
0x96bfa04d…d06b
0x34b655…2a6f
6 touches
3 conflicts
0x486aed2f…813b
0x34b655…2a6f
4 touches
1 conflict
0x58f65aa1…8f98
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
10 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity