← previous blocknext block →recent activity
Analyzing
Block #83,840,730
42 transactions · 37 stateful · 2026-06-26 15:12:27 UTC
Parallelism
67/100
Blocked
65%
Avg conflicts / tx
2.4
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,840,730 · 42 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w08w110w311w012w115w016w117w018w119w220w321w422w523w624w725w826w928w1029w1131w232w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
10 touches
10 conflicts
0xdf37a93d…879b
0x34b655…2a6f
10 touches
10 conflicts
0x8f4c5cb2…cbee
0x34b655…2a6f
10 touches
10 conflicts
0xf324b405…ca30
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
10 touches
10 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
66 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity