← previous blocknext block →recent activity
Analyzing
Block #83,655,857
17 transactions · 16 stateful · 2026-06-25 18:38:59 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
1.29
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,655,857 · 17 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
3w04w15w26w311w414w115w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0c6e179…a103
0x34b655…2a6f
12 touches
15 conflicts
0xd064a456…b881
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x85b9828d…4e52
0x34b655…2a6f
6 touches
3 conflicts
0x2c53a187…3646
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x8706ce61…c941
0x34b655…2a6f
6 touches
3 conflicts
0xb94f88a8…7eb1
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
15 conflicts on slot 0xa0c6e1796c…01a103
Audit this contract →
← previous block·next block →recent activity