← previous blocknext block →recent activity
Analyzing
Block #83,468,977
22 transactions · 16 stateful · 2026-06-24 21:52:04 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,468,977 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w011w012w113w214w315w416w518w620w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xcfcd4688…1665
0x34b655…2a6f
12 touches
15 conflicts
0xa51c97e1…6b55
0x34b655…2a6f
10 touches
10 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
10 touches
10 conflicts
0xe283e878…7262
0x34b655…2a6f
10 touches
10 conflicts
0x9610cea3…6614
0x34b655…2a6f
6 touches
3 conflicts
0x9566a5ca…7443
0x34b655…2a6f
4 touches
1 conflict
0xf9eb51e3…2715
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity