← previous blocknext block →recent activity
Analyzing
Block #82,172,033
18 transactions · 12 stateful · 2026-06-18 21:27:29 UTC
Parallelism
89/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,172,033 · 18 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
1w02w19w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62259ddc…9f4c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xfb0a4eb5…8be3
0x34b655…2a6f
3 touches
1 conflict
0xad37febf…d1eb
0x34b655…2a6f
3 touches
1 conflict
0x2951bfac…715d
0xd32edf…ff58
3 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
1 conflict on slot 0x62259ddc99…f89f4c
Audit this contract →
← previous block·next block →recent activity