← previous blocknext block →recent activity
Analyzing
Block #83,456,001
13 transactions · 11 stateful · 2026-06-24 20:25:24 UTC
Parallelism
77/100
Blocked
18%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,456,001 · 13 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
2w07w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb883652…3b26
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x1ca68aab…5e4a
0x34b655…2a6f
4 touches
1 conflict
0x5a30d8a9…f768
0x34b655…2a6f
4 touches
1 conflict
0x6aa4a080…889c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0003
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
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 0xcb883652a5…343b26
Audit this contract →
← previous block·next block →recent activity