← previous blocknext block →recent activity
Analyzing
Block #83,402,025
58 transactions · 20 stateful · 2026-06-24 14:24:48 UTC
Parallelism
90/100
Blocked
70%
Avg conflicts / tx
0.41
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,402,025 · 58 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
1w02w13w14w15w06w123w246w347w449w250w351w152w253w255w456w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71632345…6ee9
0x34b655…2a6f
8 touches
6 conflicts
0x0b16149e…7d4d
0x065c9d…c394
6 touches
3 conflicts
0xff96dc9b…93d7
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0835adb5…ad83
0x34b655…2a6f
6 touches
3 conflicts
0x60d07066…695c
0x34b655…2a6f
6 touches
3 conflicts
0x967b4a40…7a78
0x34b655…2a6f
6 touches
3 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x7163234506…a86ee9
Audit this contract →
← previous block·next block →recent activity