← previous blocknext block →recent activity
Analyzing
Block #100,093,721
19 transactions · 18 stateful · 2026-08-29 04:52:10 UTC
Parallelism
63/100
Blocked
39%
Avg conflicts / tx
0.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,093,721 · 19 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
2w06w17w210w311w414w516w618w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
6 touches
3 conflicts
0x61571888…b392
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x06f79d0a…72c6
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x2e395699…f3ca
0x34b655…2a6f
4 touches
1 conflict
0x4305865e…7907
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity