← previous blocknext block →recent activity
Analyzing
Block #83,481,662
10 transactions · 7 stateful · 2026-06-24 23:16:38 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,481,662 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x864353d4…dcb7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x206fb8db…a146
0x34b655…2a6f
3 touches
1 conflict
0x0b6cbc15…3e7c
0x34b655…2a6f
2 touches
0 conflicts
0x0e213495…6d39
0x34b655…2a6f
2 touches
0 conflicts
0x1fbf7dcc…4fea
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x864353d495…99dcb7
Audit this contract →
← previous block·next block →recent activity