← previous blocknext block →recent activity
Analyzing
Block #83,454,752
26 transactions · 24 stateful · 2026-06-24 20:17:03 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,454,752 · 26 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w014w015w016w117w119w224w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x126a0344…4465
0x34b655…2a6f
6 touches
3 conflicts
0xe9425fe7…1711
0x34b655…2a6f
6 touches
3 conflicts
0xfadc118d…5d64
0x34b655…2a6f
6 touches
3 conflicts
0x731e6d82…2883
0x065c9d…c394
6 touches
3 conflicts
0x2f7781d6…e632
0x34b655…2a6f
4 touches
1 conflict
0x388f889f…a655
0x34b655…2a6f
4 touches
1 conflict
0x5138188e…796b
0x34b655…2a6f
4 touches
1 conflict
0x7359de1f…fb28
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
3 conflicts on slot 0x126a0344b1…d04465
Audit this contract →
← previous block·next block →recent activity