← previous blocknext block →recent activity
Analyzing
Block #83,398,721
49 transactions · 38 stateful · 2026-06-24 14:02:42 UTC
Parallelism
71/100
Blocked
71%
Avg conflicts / tx
2.29
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,398,721 · 49 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w18w19w211w114w215w317w018w119w220w321w422w524w625w726w831w234w539w240w545w1246w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xffc2f21e…b393
0x34b655…2a6f
12 touches
15 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
10 touches
10 conflicts
0x9c7571b3…9605
0x34b655…2a6f
10 touches
10 conflicts
0xa1571d54…ae41
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 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
36 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity