← previous blocknext block →recent activity
Analyzing
Block #83,627,982
20 transactions · 20 stateful · 2026-06-25 15:32:52 UTC
Parallelism
70/100
Blocked
35%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,627,982 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w17w28w39w413w014w117w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x758bd24b…cc0c
0x34b655…2a6f
12 touches
15 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
10 touches
10 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
10 touches
10 conflicts
0xbb5d2c3d…ff37
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x5df421ff…59da
0x34b655…2a6f
10 touches
10 conflicts
0xa1e51cc8…e4cf
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
15 conflicts on slot 0x758bd24bd8…71cc0c
Audit this contract →
← previous block·next block →recent activity