← previous blocknext block →recent activity
Analyzing
Block #83,655,735
16 transactions · 16 stateful · 2026-06-25 18:38:10 UTC
Parallelism
50/100
Blocked
63%
Avg conflicts / tx
1.75
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,655,735 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w27w38w49w510w615w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xa0c6e179…a103
0x34b655…2a6f
10 touches
10 conflicts
0x8e730409…6b8e
0x34b655…2a6f
8 touches
6 conflicts
0xe46a9e83…22b5
0x34b655…2a6f
8 touches
6 conflicts
0xd064a456…b881
0x34b655…2a6f
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x2c53a187…3646
0x34b655…2a6f
7 touches
8 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