← previous blocknext block →recent activity
Analyzing
Block #83,671,185
17 transactions · 16 stateful · 2026-06-25 20:21:11 UTC
Parallelism
59/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,671,185 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w38w49w010w111w214w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99ee776a…053a
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x0f068b13…fb19
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x5f447bf3…57c7
0x34b655…2a6f
6 touches
3 conflicts
0x7fe97198…79ab
0x34b655…2a6f
6 touches
3 conflicts
0x8b955880…649d
0x34b655…2a6f
6 touches
3 conflicts
0xd4702f73…926c
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x99ee776a78…65053a
Audit this contract →
← previous block·next block →recent activity