← previous blocknext block →recent activity
Analyzing
Block #83,672,769
21 transactions · 20 stateful · 2026-06-25 20:31:42 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,672,769 · 21 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
3w04w15w26w07w111w115w216w317w219w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xaa7ee7…f0e4
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x206fb8db…a146
0x34b655…2a6f
5 touches
3 conflicts
0x75cdffd8…c217
0x34b655…2a6f
4 touches
1 conflict
0x864353d4…dcb7
0x34b655…2a6f
4 touches
1 conflict
0x465409b4…91bf
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x2fdfa032…139c
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: 0xaa7ee7ce…aff0e4
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity