← previous blocknext block →recent activity
Analyzing
Block #85,671,194
18 transactions · 16 stateful · 2026-07-05 02:32:17 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,671,194 · 18 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
5w07w19w011w112w115w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1830b71…6cd6
0x34b655…2a6f
6 touches
3 conflicts
0xfdde6236…b2a5
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x65db2f2f…ba40
0x34b655…2a6f
6 touches
3 conflicts
0x2e403420…263c
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
0x34b655…2a6f
4 touches
1 conflict
0x54b193ad…c830
0x34b655…2a6f
4 touches
1 conflict
0x6a84af8a…2f83
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
3 conflicts on slot 0xa1830b71ae…ca6cd6
Audit this contract →
← previous block·next block →recent activity