← previous blocknext block →recent activity
Analyzing
Block #85,536,742
10 transactions · 9 stateful · 2026-07-04 11:37:01 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,536,742 · 10 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
1w02w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x309ef367…e8a1
0x34b655…2a6f
4 touches
1 conflict
0x53b4ef2b…8a05
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x135e9e97…c954
0x40c49f…2af0
2 touches
0 conflicts
0x2373ba7f…1f3a
0x40c49f…2af0
2 touches
0 conflicts
0x64fccb89…cfcb
0x40c49f…2af0
2 touches
0 conflicts
0xd9c2bb5c…e186
0x40c49f…2af0
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 0x309ef36779…d6e8a1
Audit this contract →
← previous block·next block →recent activity