← previous blocknext block →recent activity
Analyzing
Block #100,750,735
28 transactions · 24 stateful · 2026-08-31 12:01:56 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,750,735 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w16w07w19w015w216w217w119w221w122w325w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde0291c4…ba20
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x08e8f2c9…a11a
0x34b655…2a6f
4 touches
1 conflict
0x1a3d2527…8ca0
0x34b655…2a6f
4 touches
1 conflict
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x30eb4826…3990
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
3 conflicts on slot 0xde0291c4e0…90ba20
Audit this contract →
← previous block·next block →recent activity