← previous blocknext block →recent activity
Analyzing
Block #85,249,491
12 transactions · 11 stateful · 2026-07-03 03:44:10 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,249,491 · 12 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
1w02w16w07w18w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc23f27c3…1d00
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x056ec16c…55b9
0x34b655…2a6f
4 touches
1 conflict
0x5ad3280d…16bb
0x34b655…2a6f
4 touches
1 conflict
0xb9bc4844…7044
0x34b655…2a6f
4 touches
1 conflict
0x8f1ac538…dfd4
0x40c49f…2af0
2 touches
0 conflicts
0xfa12d88f…bbe8
0x40c49f…2af0
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 0xc23f27c3e5…be1d00
Audit this contract →
← previous block·next block →recent activity