← previous blocknext block →recent activity
Analyzing
Block #100,923,222
25 transactions · 17 stateful · 2026-09-01 02:30:00 UTC
Parallelism
88/100
Blocked
24%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,923,222 · 25 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
1w07w112w214w016w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2827ae77…4368
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x141924b7…a75d
0x065c9d…c394
4 touches
1 conflict
0xec92b117…b7cd
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x1dcb4db5…dc05
0x34b655…2a6f
2 touches
0 conflicts
0x207ad3a3…f727
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 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
3 conflicts on slot 0x2827ae778d…a84368
Audit this contract →
← previous block·next block →recent activity