← previous blocknext block →recent activity
Analyzing
Block #83,625,020
26 transactions · 19 stateful · 2026-06-25 15:13:05 UTC
Parallelism
81/100
Blocked
53%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,625,020 · 26 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
2w04w17w08w19w210w311w412w014w115w219w320w424w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xaa7ee7…f0e4
10 touches
10 conflicts
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0xbbec4dcb…832e
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x827168ce…03be
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x9fbabe09…8dd6
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
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity