← previous blocknext block →recent activity
Analyzing
Block #87,587,366
18 transactions · 17 stateful · 2026-07-13 23:55:59 UTC
Parallelism
61/100
Blocked
41%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,587,366 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w28w311w412w515w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x745952b2…d90c
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf2f40f08…5cdb
0x34b655…2a6f
6 touches
3 conflicts
0x212c5b04…5f01
0x34b655…2a6f
6 touches
3 conflicts
0x2848aeee…60ee
0x34b655…2a6f
6 touches
3 conflicts
0x7584bc06…3463
0x34b655…2a6f
4 touches
1 conflict
0xfeacfacd…41d2
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity