← previous blocknext block →recent activity
Analyzing
Block #83,669,244
26 transactions · 23 stateful · 2026-06-25 20:08:15 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
1.27
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,669,244 · 26 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
1w03w14w25w27w08w110w011w112w213w314w415w516w624w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x65df2980…8edc
0x34b655…2a6f
10 touches
10 conflicts
0x913ebf0e…d816
0x34b655…2a6f
10 touches
10 conflicts
0xd4702f73…926c
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c3
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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