← previous blocknext block →recent activity
Analyzing
Block #82,018,793
100 transactions · 11 stateful · 2026-06-18 04:25:18 UTC
Parallelism
96/100
Blocked
27%
Avg conflicts / tx
0.03
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,018,793 · 100 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
72w090w194w299w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x36fa0779…82b3
0x34b655…2a6f
4 touches
1 conflict
0x1086ec16…1a17
0x34b655…2a6f
2 touches
0 conflicts
0x217bd767…b79e
0x34b655…2a6f
2 touches
0 conflicts
0x25907bcb…6181
0x34b655…2a6f
2 touches
0 conflicts
0x38d0f220…01f4
0x34b655…2a6f
2 touches
0 conflicts
0x3fc0ff64…5581
0x34b655…2a6f
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 0xf6476f21e7…f83580
Audit this contract →
← previous block·next block →recent activity