← previous blocknext block →recent activity
Analyzing
Block #83,893,315
11 transactions · 10 stateful · 2026-06-26 21:03:21 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,893,315 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xc8fec9ca…2d60
0x34b655…2a6f
5 touches
3 conflicts
0x9863393c…ce7b
0x34b655…2a6f
4 touches
2 conflicts
0x1b2c54a1…5a76
0x34b655…2a6f
4 touches
1 conflict
0xf74e1151…513d
0x34b655…2a6f
4 touches
1 conflict
0x2f892323…4500
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