← previous blocknext block →recent activity
Analyzing
Block #83,653,554
14 transactions · 12 stateful · 2026-06-25 18:23:40 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,653,554 · 14 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
5w07w18w210w113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb7c435f…f490
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x1ee4a6d2…6389
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x9b58e20f…2dd9
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc6280a03…0879
0x34b655…2a6f
4 touches
1 conflict
0xe4123854…4dc4
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
6 conflicts on slot 0xdb7c435f8d…b5f490
Audit this contract →
← previous block·next block →recent activity