← previous blocknext block →recent activity
Analyzing
Block #83,637,243
21 transactions · 21 stateful · 2026-06-25 16:34:46 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,637,243 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w27w38w09w110w415w419w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5da1f528…b8d6
0x34b655…2a6f
10 touches
10 conflicts
0x619f5683…5bd4
0x34b655…2a6f
10 touches
10 conflicts
0xf324b405…ca30
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x157dbfb2…4089
0x34b655…2a6f
6 touches
3 conflicts
0x5e4d6834…2898
0x34b655…2a6f
6 touches
3 conflicts
0x6fd62ae7…0bc0
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
10 conflicts on slot 0x5da1f5288a…00b8d6
Audit this contract →
← previous block·next block →recent activity