← previous blocknext block →recent activity
Analyzing
Block #82,497,433
23 transactions · 17 stateful · 2026-06-20 09:37:59 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,497,433 · 23 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
1w02w119w020w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x1b159f3d…9163
0x34b655…2a6f
4 touches
1 conflict
0xf9f48af5…4205
0xa6afd3…d132
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x6637e421…af93
0x34b655…2a6f
4 touches
1 conflict
0xa800bb04…1d40
0x34b655…2a6f
4 touches
1 conflict
0xe54919cc…322e
0x1efe02…37d6
2 touches
0 conflicts
0xe6f6660a…ad87
0x1efe02…37d6
2 touches
0 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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity