← previous blocknext block →recent activity
Analyzing
Block #83,028,406
14 transactions · 11 stateful · 2026-06-22 20:47:29 UTC
Parallelism
43/100
Blocked
64%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,028,406 · 14 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0x326a02b5…8dad
0x34b655…2a6f
14 touches
21 conflicts
0x08913286…f0df
0x34b655…2a6f
8 touches
6 conflicts
0x157dbfb2…4089
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0xf7e84d35…ad5c
0x34b655…2a6f
8 touches
6 conflicts
0x36a49c16…89b9
0xc8689a…ee79
8 touches
6 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
28 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity