← previous blocknext block →recent activity
Analyzing
Block #85,606,905
16 transactions · 15 stateful · 2026-07-04 19:24:23 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,606,905 · 16 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
9w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74462c1e…84f3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xed59b1cd…8509
0x34b655…2a6f
4 touches
1 conflict
0x5e0b8bbe…377b
0x34b655…2a6f
4 touches
1 conflict
0x0a6f5e37…6c3c
0x34b655…2a6f
2 touches
0 conflicts
0x4c56e2d6…0a93
0x34b655…2a6f
2 touches
0 conflicts
0x6f900be0…cd6e
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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 0x74462c1e64…b484f3
Audit this contract →
← previous block·next block →recent activity