← previous blocknext block →recent activity
Analyzing
Block #82,280,730
24 transactions · 17 stateful · 2026-06-19 09:32:12 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,280,730 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w19w010w117w120w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x689d5e98…d068
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3e1c3586…83d7
0xa6afd3…d132
4 touches
1 conflict
0x08913286…f0df
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x388f889f…a655
0x34b655…2a6f
4 touches
1 conflict
0x8388eab6…83ff
0x34b655…2a6f
4 touches
1 conflict
0xbde30d77…b032
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
3 conflicts on slot 0x689d5e9882…e1d068
Audit this contract →
← previous block·next block →recent activity