← previous blocknext block →recent activity
Analyzing
Block #87,705,312
18 transactions · 18 stateful · 2026-07-14 13:04:39 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,705,312 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w27w08w110w011w312w413w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa38eb2fc…1659
0x34b655…2a6f
10 touches
10 conflicts
0xa38eb2fc…1658
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x91ac6bd6…3754
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
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 0xa38eb2fcd4…781659
Audit this contract →
← previous block·next block →recent activity