← previous blocknext block →recent activity
Analyzing
Block #83,760,097
15 transactions · 14 stateful · 2026-06-26 06:14:22 UTC
Parallelism
53/100
Blocked
50%
Avg conflicts / tx
1.73
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,760,097 · 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
4w05w16w27w39w410w513w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x505f101e…7ad6
0x34b655…2a6f
10 touches
10 conflicts
0xc9493039…ea3b
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x28f402c6…cb12
0x34b655…2a6f
8 touches
6 conflicts
0x39b19fdd…e417
0x34b655…2a6f
8 touches
6 conflicts
0x7506443a…4820
0x34b655…2a6f
8 touches
6 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 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity