← previous blocknext block →recent activity
Analyzing
Block #87,315,411
18 transactions · 17 stateful · 2026-07-12 17:36:26 UTC
Parallelism
56/100
Blocked
59%
Avg conflicts / tx
1.67
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,315,411 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w38w49w511w614w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ea6a117…f2f2
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x924bac95…3f39
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1ae
0xb1dbf0…c0d3
6 touches
3 conflicts
0x548145a9…cfce
0x34b655…2a6f
6 touches
3 conflicts
0x63b15849…80b2
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0x7ea6a11745…1df2f2
Audit this contract →
← previous block·next block →recent activity