← previous blocknext block →recent activity
Analyzing
Block #83,398,871
32 transactions · 23 stateful · 2026-06-24 14:03:43 UTC
Parallelism
69/100
Blocked
61%
Avg conflicts / tx
1.34
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #83,398,871 · 32 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w414w015w116w217w318w419w520w628w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x0835adb5…ad83
0x34b655…2a6f
8 touches
6 conflicts
0x901d9f30…67a4
0x34b655…2a6f
8 touches
6 conflicts
0x757b0543…e087
0x34b655…2a6f
6 touches
3 conflicts
0x7e6c970a…65af
0x34b655…2a6f
6 touches
3 conflicts
0x9c7571b3…9605
0x34b655…2a6f
6 touches
3 conflicts
0xa1571d54…ae41
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity