← previous blocknext block →recent activity
Analyzing
Block #83,582,773
11 transactions · 10 stateful · 2026-06-25 10:30:52 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,582,773 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xa1acfc3c…978d
0x34b655…2a6f
4 touches
1 conflict
0x77ea60f4…e7ca
0x34b655…2a6f
4 touches
1 conflict
0x191efc73…e7ba
0x34b655…2a6f
2 touches
0 conflicts
0x361e4d88…9b44
0x34b655…2a6f
2 touches
0 conflicts
0x37c1e71a…7d40
0x34b655…2a6f
2 touches
0 conflicts
0x65bb8d8c…8bb0
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x9a3068dd84…9918f0
Audit this contract →
← previous block·next block →recent activity