← previous blocknext block →recent activity
Analyzing
Block #87,283,068
30 transactions · 25 stateful · 2026-07-12 14:00:11 UTC
Parallelism
87/100
Blocked
40%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,283,068 · 30 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
9w010w111w012w114w017w018w119w221w222w023w324w125w226w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
6 touches
3 conflicts
0x0178c2de…b37d
0xb1dbf0…c0d3
6 touches
3 conflicts
0x36077f58…66cd
0x34b655…2a6f
4 touches
1 conflict
0x4688dd30…ef52
0x34b655…2a6f
4 touches
1 conflict
0x4b8a36c9…0562
0x34b655…2a6f
4 touches
1 conflict
0x4b8b3363…6632
0x34b655…2a6f
4 touches
1 conflict
0x685c78f5…3a47
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 0xa7013be2a1…9ac0a8
Audit this contract →
← previous block·next block →recent activity