← previous blocknext block →recent activity
Analyzing
Block #83,875,471
13 transactions · 13 stateful · 2026-06-26 19:04:16 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,875,471 · 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
9w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x4bdcc5ee…7e90
0x34b655…2a6f
6 touches
3 conflicts
0xf0e15584…b5a3
0x34b655…2a6f
4 touches
1 conflict
0x190ab6a6…5132
0x34b655…2a6f
4 touches
1 conflict
0x35df8834…14b8
0x34b655…2a6f
4 touches
1 conflict
0x5a53a606…9b42
0x34b655…2a6f
4 touches
1 conflict
0x63860705…3e2e
0x34b655…2a6f
4 touches
1 conflict
0x810a3aa2…0227
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity