← previous blocknext block →recent activity
Analyzing
Block #83,661,889
13 transactions · 12 stateful · 2026-06-25 19:19:09 UTC
Parallelism
54/100
Blocked
42%
Avg conflicts / tx
0.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,661,889 · 13 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
3w04w15w27w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x672fd8ba…9e9e
0x34b655…2a6f
5 touches
3 conflicts
0xf56a57b1…3e2a
0x34b655…2a6f
4 touches
1 conflict
0xf8716a36…8787
0x34b655…2a6f
4 touches
1 conflict
0x505f101e…7ad6
0x34b655…2a6f
4 touches
1 conflict
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0xb17a0fda…3fa9
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
3 conflicts on slot 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity