← previous blocknext block →recent activity
Analyzing
Block #83,665,552
20 transactions · 17 stateful · 2026-06-25 19:43:34 UTC
Parallelism
75/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,665,552 · 20 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
1w02w15w06w17w08w29w310w011w413w016w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
6 touches
3 conflicts
0x3cf50d44…961b
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x3e776e71…4bbf
0x34b655…2a6f
4 touches
1 conflict
0x47fadd12…dcdd
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity