← previous blocknext block →recent activity
Analyzing
Block #83,662,131
22 transactions · 21 stateful · 2026-06-25 19:20:46 UTC
Parallelism
82/100
Blocked
48%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,662,131 · 22 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
3w04w15w26w07w19w110w211w314w015w216w117w321w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37a276a3…673f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xaa7ee7…f0e4
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc983cab3…daa5
0x34b655…2a6f
4 touches
1 conflict
0xcd63138b…63d9
0x34b655…2a6f
4 touches
1 conflict
0xd5d0a749…c426
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 0x37a276a33f…0f673f
Audit this contract →
← previous block·next block →recent activity