← previous blocknext block →recent activity
Analyzing
Block #87,347,293
11 transactions · 10 stateful · 2026-07-12 21:09:38 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,347,293 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ae9d2df…f787
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xbb277c58…e388
0x34b655…2a6f
6 touches
3 conflicts
0x0ae9d2df…f788
0x34b655…2a6f
4 touches
1 conflict
0x0edff147…13ed
0x34b655…2a6f
4 touches
1 conflict
0x401ab686…d1c2
0x34b655…2a6f
4 touches
1 conflict
0x5a7eb2ab…75a0
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 0x0ae9d2df9c…16f787
Audit this contract →
← previous block·next block →recent activity