← previous blocknext block →recent activity
Analyzing
Block #85,108,313
18 transactions · 16 stateful · 2026-07-02 12:03:05 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,108,313 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w210w311w216w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ec64628…72e4
0x34b655…2a6f
7 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xcfa965cc…6fcf
0x34b655…2a6f
6 touches
3 conflicts
0xf324b405…ca30
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x98be801c…d7c3
0x34b655…2a6f
4 touches
1 conflict
0xa0efa7bc…8b24
0x34b655…2a6f
4 touches
1 conflict
0xa457c06e…2f06
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 0x5ec6462858…6272e4
Audit this contract →
← previous block·next block →recent activity