← previous blocknext block →recent activity
Analyzing
Block #83,656,174
29 transactions · 22 stateful · 2026-06-25 18:41:05 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,656,174 · 29 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
4w05w06w111w012w113w114w215w316w417w525w227w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d7f309d…5145
0x34b655…2a6f
12 touches
15 conflicts
0x705f195d…cc32
0x34b655…2a6f
12 touches
15 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x886684d5…89dd
0x34b655…2a6f
10 touches
10 conflicts
0x7506443a…4820
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x53e102b7…c71c
0x34b655…2a6f
8 touches
6 conflicts
0xc62fc5e4…95ae
0x34b655…2a6f
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
15 conflicts on slot 0x5d7f309de2…775145
Audit this contract →
← previous block·next block →recent activity