← previous blocknext block →recent activity
Analyzing
Block #83,664,948
17 transactions · 17 stateful · 2026-06-25 19:39:33 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,664,948 · 17 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
2w03w14w15w29w010w212w013w014w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1526f9e…82d5
0x34b655…2a6f
8 touches
6 conflicts
0xee5155c8…1730
0x34b655…2a6f
6 touches
3 conflicts
0x2fdfa032…139c
0x34b655…2a6f
6 touches
3 conflicts
0x374fc18a…6998
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x698ea162…269e
0x34b655…2a6f
4 touches
1 conflict
0x6b47245e…a342
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
6 conflicts on slot 0xc1526f9e7b…c282d5
Audit this contract →
← previous block·next block →recent activity