← previous blocknext block →recent activity
Analyzing
Block #83,398,634
23 transactions · 19 stateful · 2026-06-24 14:02:07 UTC
Parallelism
70/100
Blocked
58%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,398,634 · 23 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
4w05w16w27w39w410w512w014w115w216w017w118w220w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xa1571d54…ae41
0x34b655…2a6f
8 touches
6 conflicts
0xd2053580…246d
0x34b655…2a6f
8 touches
6 conflicts
0x9c7571b3…9605
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x0835adb5…ad83
0x34b655…2a6f
7 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity