← previous blocknext block →recent activity
Analyzing
Block #85,350,103
11 transactions · 10 stateful · 2026-07-03 14:54:21 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,350,103 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5accb062…6d13
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
0x34b655…2a6f
4 touches
1 conflict
0x98fc5672…13c7
0x34b655…2a6f
4 touches
1 conflict
0xaa437be8…ee54
0x34b655…2a6f
4 touches
1 conflict
0xb2082b87…a881
0x34b655…2a6f
4 touches
1 conflict
0xb75d9839…c7bd
0x34b655…2a6f
4 touches
1 conflict
0xb874323e…7566
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
3 conflicts on slot 0x5accb062f9…b96d13
Audit this contract →
← previous block·next block →recent activity