← previous blocknext block →recent activity
Analyzing
Block #100,751,377
22 transactions · 19 stateful · 2026-08-31 12:05:09 UTC
Parallelism
73/100
Blocked
32%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,751,377 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w19w211w312w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a3ed075…b9fe
0x34b655…2a6f
10 touches
10 conflicts
0x9482a067…eba9
0x34b655…2a6f
6 touches
3 conflicts
0x2c2761c0…476e
0x34b655…2a6f
6 touches
3 conflicts
0x8180b2cc…22c7
0x34b655…2a6f
6 touches
3 conflicts
0x44b72d07…f4ba
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
10 conflicts on slot 0x4a3ed0758f…dbb9fe
Audit this contract →
← previous block·next block →recent activity