← previous blocknext block →recent activity
Analyzing
Block #85,794,949
18 transactions · 16 stateful · 2026-07-05 16:17:38 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,794,949 · 18 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
2w07w08w111w112w016w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01414ad2…98ec
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0x1b3cd6b8…47aa
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x4e638546…0894
0x34b655…2a6f
4 touches
1 conflict
0x636299bd…db71
0x34b655…2a6f
4 touches
1 conflict
0x795b889e…2c24
0x34b655…2a6f
4 touches
1 conflict
0x8c1bae25…2642
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
1 conflict on slot 0x01414ad233…5e98ec
Audit this contract →
← previous block·next block →recent activity