← previous blocknext block →recent activity
Analyzing
Block #82,971,021
16 transactions · 10 stateful · 2026-06-22 14:23:30 UTC
Parallelism
75/100
Blocked
30%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,971,021 · 16 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
5w08w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f21840f…6cde
0x34b655…2a6f
8 touches
6 conflicts
0xa51de3df…c65a
0x34b655…2a6f
4 touches
1 conflict
0xc7ac2c0f…f591
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x006c3b86…59a9
0x34b655…2a6f
4 touches
1 conflict
0x11a31856…cbd8
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
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 0x0f21840f7c…c86cde
Audit this contract →
← previous block·next block →recent activity