← previous blocknext block →recent activity
Analyzing
Block #85,272,938
21 transactions · 18 stateful · 2026-07-03 06:20:17 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,272,938 · 21 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
1w02w19w010w111w214w219w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eac6378…36f4
0x34b655…2a6f
6 touches
3 conflicts
0x90e113f8…c8f9
0xc8689a…ee79
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x4bfbf321…d4f2
0x34b655…2a6f
6 touches
3 conflicts
0xa74dbf9d…7a49
0xd32edf…ff58
5 touches
3 conflicts
0xe19cbaaf…3b90
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
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 0x0eac637818…cb36f4
Audit this contract →
← previous block·next block →recent activity