← previous blocknext block →recent activity
Analyzing
Block #82,328,261
29 transactions · 19 stateful · 2026-06-19 14:49:13 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,328,261 · 29 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
5w06w113w014w118w019w123w225w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x957c875f…b3f9
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xf6884b1c…8b7f
0x34b655…2a6f
8 touches
6 conflicts
0x9a3068dd…18f0
0x34b655…2a6f
8 touches
6 conflicts
0x6d2b3208…181c
0x34b655…2a6f
6 touches
3 conflicts
0x62363b97…ab37
0x34b655…2a6f
5 touches
3 conflicts
0xa25d60d4…d238
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 0x957c875f2a…99b3f9
Audit this contract →
← previous block·next block →recent activity