← previous blocknext block →recent activity
Analyzing
Block #82,739,094
8 transactions · 6 stateful · 2026-06-21 12:34:03 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,739,094 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe732567d…b65d
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0x76ed8777…1e5f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x72a152dd…a0a6
0x16f70c…c3dd
2 touches
0 conflicts
0x0bcd2258…2897
0x58e158…3d57
2 touches
0 conflicts
0x77bc4331…5ae5
0x96b79e…d00a
2 touches
0 conflicts
0xcd342fd8…4e95
0x96b79e…d00a
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
1 conflict on slot 0xe732567db9…26b65d
Audit this contract →
← previous block·next block →recent activity