← previous blocknext block →recent activity
Analyzing
Block #100,787,924
21 transactions · 18 stateful · 2026-08-31 15:09:10 UTC
Parallelism
86/100
Blocked
39%
Avg conflicts / tx
0.52
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,787,924 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w110w011w113w214w015w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb63aef0…7f87
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x7048e456…4cb7
0x34b655…2a6f
4 touches
1 conflict
0x715f200b…9e79
0x34b655…2a6f
4 touches
1 conflict
0x8311570f…5321
0x34b655…2a6f
4 touches
1 conflict
0x9482a067…eba9
0x34b655…2a6f
4 touches
1 conflict
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0xdb63aef0d6…697f87
Audit this contract →
← previous block·next block →recent activity