← previous blocknext block →recent activity
Analyzing
Block #100,750,763
32 transactions · 28 stateful · 2026-08-31 12:02:04 UTC
Parallelism
78/100
Blocked
64%
Avg conflicts / tx
1.28
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,750,763 · 32 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w110w211w213w214w320w321w422w323w224w425w527w231w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68531239…e9a3
0x34b655…2a6f
10 touches
10 conflicts
0x6232d418…4d29
0xd32edf…ff58
9 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x1d9154e7…8821
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x89ac61bf…9443
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0x68531239f9…5ae9a3
Audit this contract →
← previous block·next block →recent activity