← previous blocknext block →recent activity
Analyzing
Block #83,638,860
15 transactions · 14 stateful · 2026-06-25 16:45:33 UTC
Parallelism
53/100
Blocked
43%
Avg conflicts / tx
1.53
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,638,860 · 15 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w37w410w013w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x049cca71…b102
0x34b655…2a6f
14 touches
21 conflicts
0x09bdec97…b844
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x157dbfb2…4089
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x7d96b301…de24
0x34b655…2a6f
6 touches
3 conflicts
0xbb3504d4…b05f
0x34b655…2a6f
6 touches
3 conflicts
0xe64e6363…e676
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
21 conflicts on slot 0x049cca710d…16b102
Audit this contract →
← previous block·next block →recent activity