← previous blocknext block →recent activity
Analyzing
Block #83,356,184
25 transactions · 18 stateful · 2026-06-24 09:18:25 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,356,184 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w18w09w110w211w313w119w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xf8372997…869e
0x34b655…2a6f
6 touches
3 conflicts
0x8a01f41e…d4bf
0x34b655…2a6f
6 touches
3 conflicts
0xb0e9898d…42c2
0xa6afd3…d132
6 touches
3 conflicts
0x3b2f7093…f8b1
0x34b655…2a6f
4 touches
1 conflict
0x5a30d8a9…f768
0x34b655…2a6f
4 touches
1 conflict
0x5d2b5661…df66
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