← previous blocknext block →recent activity
Analyzing
Block #85,761,672
11 transactions · 10 stateful · 2026-07-05 12:36:02 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,761,672 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x4a7e91bb…d690
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b3a72d1…718e
0x065c9d…c394
4 touches
1 conflict
0xaaa31da8…b680
0x065c9d…c394
3 touches
1 conflict
0xd986481e…3ec9
0x065c9d…c394
3 touches
1 conflict
0x2fb70332…4834
0x065c9d…c394
3 touches
1 conflict
0x3378e8b6…20a9
0x754704…b603
2 touches
0 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
1 conflict on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity