← previous blocknext block →recent activity
Analyzing
Block #83,667,088
11 transactions · 11 stateful · 2026-06-25 19:53:51 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,667,088 · 11 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
3w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73ca2093…8dd6
0x34b655…2a6f
8 touches
6 conflicts
0xc8615e83…8e8b
0x34b655…2a6f
8 touches
6 conflicts
0x705f195d…cc32
0x34b655…2a6f
8 touches
6 conflicts
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x374fc18a…6998
0x34b655…2a6f
4 touches
1 conflict
0x4dd09ed2…77fb
0x34b655…2a6f
4 touches
1 conflict
0x5ab86fdb…69ec
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
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 0x73ca209343…408dd6
Audit this contract →
← previous block·next block →recent activity