← previous blocknext block →recent activity
Analyzing
Block #83,630,011
31 transactions · 23 stateful · 2026-06-25 15:46:25 UTC
Parallelism
87/100
Blocked
39%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,630,011 · 31 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
5w07w19w011w112w013w114w215w017w218w120w021w122w225w029w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xaa7ee7…f0e4
6 touches
3 conflicts
0x07a0dea2…ca8c
0x34b655…2a6f
6 touches
3 conflicts
0x785889c9…0603
0x34b655…2a6f
4 touches
1 conflict
0x7d842dff…4a02
0x34b655…2a6f
4 touches
1 conflict
0x82dd2252…e1ce
0x34b655…2a6f
4 touches
1 conflict
0x87f7111a…b2ab
0x34b655…2a6f
4 touches
1 conflict
0x98d3fc79…df78
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity