← previous blocknext block →recent activity
Analyzing
Block #83,456,215
37 transactions · 31 stateful · 2026-06-24 20:26:50 UTC
Parallelism
60/100
Blocked
74%
Avg conflicts / tx
2.32
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #83,456,215 · 37 txs across 15 waves · depth 15
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
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w410w011w112w213w314w415w516w617w718w819w920w521w623w724w627w832w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
20 touches
45 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xdf37a93d…879b
0x34b655…2a6f
8 touches
6 conflicts
0x985a9b71…18bc
0x34b655…2a6f
8 touches
6 conflicts
0x731e6d82…2883
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
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
45 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity