← previous blocknext block →recent activity
Analyzing
Block #85,105,454
24 transactions · 12 stateful · 2026-07-02 11:44:00 UTC
Parallelism
92/100
Blocked
17%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,105,454 · 24 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
2w03w14w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x05b08ce0…eaa5
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x5c3cb0f1…a9fa
0x34b655…2a6f
2 touches
0 conflicts
0x5c591136…d322
0x34b655…2a6f
2 touches
0 conflicts
0x655ebe42…a56a
0x34b655…2a6f
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 0xe5bb3628b5…71e5e8
Audit this contract →
← previous block·next block →recent activity