← previous blocknext block →recent activity
Analyzing
Block #83,398,857
16 transactions · 9 stateful · 2026-06-24 14:03:37 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,398,857 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w08w19w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0x71632345…6ee9
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x5ebfe3e4…e0f2
0x34b655…2a6f
4 touches
1 conflict
0x6f1a10f8…5a04
0x34b655…2a6f
4 touches
1 conflict
0x967b4a40…7a78
0x34b655…2a6f
4 touches
1 conflict
0xb6632320…a3ce
0x34b655…2a6f
4 touches
1 conflict
0xc2ab3ad1…a6bc
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
6 conflicts on slot 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity