← previous blocknext block →recent activity
Analyzing
Block #83,356,183
17 transactions · 14 stateful · 2026-06-24 09:18:25 UTC
Parallelism
76/100
Blocked
21%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,356,183 · 17 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
2w03w14w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8372997…869e
0x34b655…2a6f
8 touches
6 conflicts
0x07795bae…cd0a
0x34b655…2a6f
6 touches
3 conflicts
0x18cbab19…7a73
0x34b655…2a6f
6 touches
3 conflicts
0x23738a2a…8ab8
0x34b655…2a6f
6 touches
3 conflicts
0x25da59fd…fb0f
0x34b655…2a6f
6 touches
3 conflicts
0x3b2f7093…f8b1
0x34b655…2a6f
6 touches
3 conflicts
0x4ae41580…a02b
0x34b655…2a6f
6 touches
3 conflicts
0x5a30d8a9…f768
0x34b655…2a6f
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
6 conflicts on slot 0xf8372997e5…13869e
Audit this contract →
← previous block·next block →recent activity