← previous blocknext block →recent activity
Analyzing
Block #85,249,823
8 transactions · 6 stateful · 2026-07-03 03:46:23 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,249,823 · 8 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xceb535f3…19cf
0x34b655…2a6f
4 touches
1 conflict
0x72a152dd…9dc7
0x16f70c…c3dd
2 touches
0 conflicts
0x01e7b865…6e70
0x188d58…ea8e
2 touches
0 conflicts
0x87b4705e…be7b
0x188d58…ea8e
2 touches
0 conflicts
0xb014a9a5…a5cc
0x188d58…ea8e
2 touches
0 conflicts
0x0110331c…b891
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity