← previous blocknext block →recent activity
Analyzing
Block #83,356,240
18 transactions · 15 stateful · 2026-06-24 09:18:48 UTC
Parallelism
78/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,356,240 · 18 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
5w06w19w215w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ca68aab…5e4a
0x34b655…2a6f
6 touches
3 conflicts
0xf8372997…869e
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x31285139…927a
0x34b655…2a6f
4 touches
1 conflict
0x4feb8e4d…dbb1
0x34b655…2a6f
4 touches
1 conflict
0x57be321f…fecc
0x34b655…2a6f
4 touches
1 conflict
0x5d2b5661…df66
0x34b655…2a6f
4 touches
1 conflict
0x6e139fcf…d36b
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 0x1ca68aab2e…3d5e4a
Audit this contract →
← previous block·next block →recent activity