← previous blocknext block →recent activity
Analyzing
Block #83,637,210
16 transactions · 15 stateful · 2026-06-25 16:34:33 UTC
Parallelism
75/100
Blocked
20%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,637,210 · 16 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
3w04w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf997c4c7…617d
0x34b655…2a6f
6 touches
3 conflicts
0xf324b405…ca30
0x34b655…2a6f
6 touches
3 conflicts
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x2b2dce58…2f1d
0x34b655…2a6f
4 touches
1 conflict
0x573dcb01…4085
0x34b655…2a6f
4 touches
1 conflict
0x5e4d6834…2898
0x34b655…2a6f
4 touches
1 conflict
0x5f96e827…8ed2
0x34b655…2a6f
4 touches
1 conflict
0x6efaef26…b534
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 0xf997c4c76f…f2617d
Audit this contract →
← previous block·next block →recent activity