← previous blocknext block →recent activity
Analyzing
Block #83,482,138
14 transactions · 10 stateful · 2026-06-24 23:19:48 UTC
Parallelism
50/100
Blocked
70%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,482,138 · 14 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
2w03w14w25w06w110w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7527802e…2ba9
0x34b655…2a6f
8 touches
9 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x756ad195…36a3
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfbf0b409…2ac6
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 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
9 conflicts on slot 0x7527802eb9…2a2ba9
Audit this contract →
← previous block·next block →recent activity