← previous blocknext block →recent activity
Analyzing
Block #100,441,076
17 transactions · 16 stateful · 2026-08-30 10:04:07 UTC
Parallelism
47/100
Blocked
56%
Avg conflicts / tx
2.18
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,441,076 · 17 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w06w17w28w311w412w513w614w715w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfce7dfe…5053
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…641f
0x34b655…2a6f
10 touches
10 conflicts
0x9e5285b4…43c1
0x34b655…2a6f
10 touches
10 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x9cf9008a…d826
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0xdfce7dfe53…c75053
Audit this contract →
← previous block·next block →recent activity