← previous blocknext block →recent activity
Analyzing
Block #83,398,063
23 transactions · 19 stateful · 2026-06-24 13:58:18 UTC
Parallelism
74/100
Blocked
58%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,398,063 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w16w28w09w110w211w312w413w521w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x124be23b…2cca
0x34b655…2a6f
10 touches
10 conflicts
0xa1571d54…ae41
0x34b655…2a6f
8 touches
6 conflicts
0xeeaac7c3…90f0
0x34b655…2a6f
8 touches
6 conflicts
0xf7c7de4c…f9d2
0x34b655…2a6f
8 touches
6 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x9c7571b3…9605
0x34b655…2a6f
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity