← previous blocknext block →recent activity
Analyzing
Block #85,281,750
10 transactions · 10 stateful · 2026-07-03 07:18:59 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,281,750 · 10 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
4w06w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x077d58c3…8ed7
0x34b655…2a6f
4 touches
1 conflict
0x64c8a24d…2887
0x34b655…2a6f
4 touches
1 conflict
0xd19c9d38…b459
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdc568d84…62d9
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x1757b8ff…9a71
0x34b655…2a6f
2 touches
0 conflicts
0x1d61a1c5…9fe6
0x34b655…2a6f
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 0x077d58c3dc…178ed7
Audit this contract →
← previous block·next block →recent activity