← previous blocknext block →recent activity
Analyzing
Block #83,633,353
22 transactions · 19 stateful · 2026-06-25 16:08:45 UTC
Parallelism
73/100
Blocked
53%
Avg conflicts / tx
0.91
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,633,353 · 22 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
3w04w15w26w310w011w112w213w314w418w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0xaa7ee7…f0e4
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x4abf223d…0915
0x34b655…2a6f
4 touches
1 conflict
0x5cc8dd43…8cf2
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x9ac79c76…c4a9
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity