← previous blocknext block →recent activity
Analyzing
Block #85,509,938
12 transactions · 11 stateful · 2026-07-04 08:38:33 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,509,938 · 12 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
5w06w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54b193ad…c830
0x34b655…2a6f
4 touches
1 conflict
0x5dd1f5d4…deac
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x19f40fdd…c416
0x065c9d…c394
2 touches
0 conflicts
0x211a1e9b…d1e7
0x065c9d…c394
2 touches
0 conflicts
0x86e5693a…f140
0x065c9d…c394
2 touches
0 conflicts
0x9792dd60…1db6
0x065c9d…c394
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 0x54b193ad55…f5c830
Audit this contract →
← previous block·next block →recent activity