← previous blocknext block →recent activity
Analyzing
Block #85,808,348
8 transactions · 7 stateful · 2026-07-05 17:46:57 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,808,348 · 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
1w02w13w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d0eaae2…60b7
0x34b655…2a6f
4 touches
1 conflict
0xfbc0b4f9…7a2c
0x34b655…2a6f
4 touches
1 conflict
0xfefb0189…f726
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x09676bb2…e014
0x40c49f…2af0
2 touches
0 conflicts
0x0aaafe33…820f
0x40c49f…2af0
2 touches
0 conflicts
0x79e39ede…5f86
0x40c49f…2af0
2 touches
0 conflicts
0xac539737…a0f9
0x40c49f…2af0
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 0x7d0eaae22e…4260b7
Audit this contract →
← previous block·next block →recent activity