← previous blocknext block →recent activity
Analyzing
Block #83,671,163
13 transactions · 12 stateful · 2026-06-25 20:21:02 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.92
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,671,163 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w17w19w010w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x913ebf0e…d816
0x34b655…2a6f
8 touches
6 conflicts
0x68c6b2fa…098d
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x249d8bcb…69b9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
0x34b655…2a6f
4 touches
1 conflict
0x65df2980…8edc
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
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 0x913ebf0e0a…d2d816
Audit this contract →
← previous block·next block →recent activity