← previous blocknext block →recent activity
Analyzing
Block #87,616,587
19 transactions · 14 stateful · 2026-07-14 03:11:25 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.16
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,616,587 · 19 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
2w03w04w15w17w28w39w413w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e970d38…d1c4
0x34b655…2a6f
12 touches
15 conflicts
0x8252706a…7ca5
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0376dd2e…48ad
0x34b655…2a6f
6 touches
3 conflicts
0x220a8541…6431
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
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
15 conflicts on slot 0x4e970d38f3…11d1c4
Audit this contract →
← previous block·next block →recent activity