← previous blocknext block →recent activity
Analyzing
Block #83,398,232
25 transactions · 19 stateful · 2026-06-24 13:59:26 UTC
Parallelism
68/100
Blocked
58%
Avg conflicts / tx
1.12
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,398,232 · 25 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
1w03w15w27w311w012w113w214w315w418w019w422w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58397d66…a6bc
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x13aceb70…cf9f
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x63b58b06…4d28
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0xa51c97e1…6b55
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
10 conflicts on slot 0x58397d66c1…2ea6bc
Audit this contract →
← previous block·next block →recent activity