← previous blocknext block →recent activity
Analyzing
Block #85,854,817
30 transactions · 22 stateful · 2026-07-05 22:56:31 UTC
Parallelism
87/100
Blocked
32%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,854,817 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w18w110w011w117w018w125w026w127w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x26784e10…ca1f
0x34b655…2a6f
4 touches
1 conflict
0x388f889f…a655
0x34b655…2a6f
4 touches
1 conflict
0x54a035dd…16c6
0x34b655…2a6f
4 touches
1 conflict
0x6637e421…af93
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity