← previous blocknext block →recent activity
Analyzing
Block #85,787,435
21 transactions · 19 stateful · 2026-07-05 15:27:33 UTC
Parallelism
81/100
Blocked
37%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,787,435 · 21 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
2w04w05w18w19w110w217w018w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5a9274d…78d7
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xda46a376…f6a6
0x34b655…2a6f
6 touches
3 conflicts
0x25957369…c648
0x34b655…2a6f
4 touches
1 conflict
0x408d584a…8309
0x34b655…2a6f
4 touches
1 conflict
0x4a11a172…dbef
0x34b655…2a6f
4 touches
1 conflict
0x6934b90c…a9cb
0x34b655…2a6f
4 touches
1 conflict
0x6c26d635…1bbf
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 0xe5a9274d87…0678d7
Audit this contract →
← previous block·next block →recent activity