← previous blocknext block →recent activity
Analyzing
Block #83,667,836
16 transactions · 12 stateful · 2026-06-25 19:58:50 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,667,836 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w08w212w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7527802e…2ba9
0x34b655…2a6f
8 touches
6 conflicts
0x756ad195…36a3
0x34b655…2a6f
8 touches
6 conflicts
0x7fe97198…79ab
0x34b655…2a6f
6 touches
3 conflicts
0x329f2f7d…dcff
0x34b655…2a6f
6 touches
3 conflicts
0x374fc18a…6998
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x60c6a924…94de
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
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 0x7527802eb9…2a2ba9
Audit this contract →
← previous block·next block →recent activity