← previous blocknext block →recent activity
Analyzing
Block #85,760,900
11 transactions · 8 stateful · 2026-07-05 12:30:53 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,760,900 · 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
4w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x972ba01f…cb84
0x34b655…2a6f
4 touches
1 conflict
0x2043e719…ff9c
0x34b655…2a6f
4 touches
1 conflict
0xd7b5bf58…1912
0x34b655…2a6f
3 touches
1 conflict
0x94dbdbab…026c
0x065c9d…c394
2 touches
0 conflicts
0x95e2f998…41be
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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