← previous blocknext block →recent activity
Analyzing
Block #83,874,526
29 transactions · 24 stateful · 2026-06-26 18:57:58 UTC
Parallelism
86/100
Blocked
46%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,874,526 · 29 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
3w04w15w26w07w19w013w014w115w216w321w222w023w124w326w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5970b31…f34c
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x5da4ed2f…283f
0xa6afd3…d132
6 touches
3 conflicts
0xd2cdfa3f…f071
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xf8fd1cbd…d093
0x34b655…2a6f
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
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 0xf5970b3144…10f34c
Audit this contract →
← previous block·next block →recent activity