← previous blocknext block →recent activity
Analyzing
Block #85,890,944
17 transactions · 11 stateful · 2026-07-06 02:57:00 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,890,944 · 17 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
2w03w16w07w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda3d9c9d…a3cc
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
2 touches
0 conflicts
0x5cc231f5…f1cd
0x69df8a…6292
2 touches
0 conflicts
0x7a12283f…b18a
0x69df8a…6292
2 touches
0 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
2 touches
0 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
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 0xda3d9c9da6…ffa3cc
Audit this contract →
← previous block·next block →recent activity