← previous blocknext block →recent activity
Analyzing
Block #85,249,444
24 transactions · 19 stateful · 2026-07-03 03:43:51 UTC
Parallelism
63/100
Blocked
63%
Avg conflicts / tx
1.17
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #85,249,444 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w08w09w110w213w114w316w417w220w521w622w723w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
12 touches
15 conflicts
0x27f2c756…0ffc
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0x4233ce00…6a67
0x34b655…2a6f
6 touches
3 conflicts
0x056ec16c…55b9
0x34b655…2a6f
6 touches
3 conflicts
0xedbfc72a…28c3
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity