← previous blocknext block →recent activity
Analyzing
Block #82,965,372
17 transactions · 16 stateful · 2026-06-22 13:45:44 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,965,372 · 17 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
1w02w14w05w16w27w38w09w110w112w314w416w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x08913286…f0df
0x34b655…2a6f
8 touches
6 conflicts
0x894c3474…190f
0x34b655…2a6f
8 touches
6 conflicts
0x410719d7…aabe
0x34b655…2a6f
8 touches
6 conflicts
0x36a49c16…89b9
0xc8689a…ee79
6 touches
3 conflicts
0xf324b405…ca30
0x34b655…2a6f
6 touches
3 conflicts
0xfb859416…558c
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity