← previous blocknext block →recent activity
Analyzing
Block #87,587,683
19 transactions · 17 stateful · 2026-07-13 23:58:06 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.16
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,587,683 · 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
2w04w15w27w08w19w210w311w412w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x745952b2…d90c
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xd64c1971…1bf2
0x34b655…2a6f
8 touches
6 conflicts
0xfd02114c…64e7
0x34b655…2a6f
6 touches
3 conflicts
0x5036f376…c06a
0x34b655…2a6f
6 touches
3 conflicts
0xb568bd0a…0a72
0x34b655…2a6f
6 touches
3 conflicts
0xb568bd0a…0a73
0x34b655…2a6f
6 touches
3 conflicts
0xc2f84a16…86b8
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
10 conflicts on slot 0x745952b2a0…a6d90c
Audit this contract →
← previous block·next block →recent activity