← previous blocknext block →recent activity
Analyzing
Block #85,224,733
17 transactions · 16 stateful · 2026-07-03 00:59:10 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,224,733 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w07w08w010w111w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x678a8de3…7da5
0x34b655…2a6f
6 touches
3 conflicts
0x170e4e4c…2b90
0x34b655…2a6f
4 touches
1 conflict
0x274b85f7…c526
0x34b655…2a6f
4 touches
1 conflict
0x4a0db291…8568
0x34b655…2a6f
4 touches
1 conflict
0x5f16286b…7e43
0x34b655…2a6f
4 touches
1 conflict
0x6f416797…c8de
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb44564d6…bb43
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 0x678a8de356…df7da5
Audit this contract →
← previous block·next block →recent activity