← previous blocknext block →recent activity
Analyzing
Block #100,739,893
45 transactions · 40 stateful · 2026-08-31 11:07:24 UTC
Parallelism
71/100
Blocked
60%
Avg conflicts / tx
1.73
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #100,739,893 · 45 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w06w07w08w111w212w213w115w216w317w418w520w621w323w724w625w126w227w328w429w530w132w841w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x623b23c5…3eff
0x34b655…2a6f
16 touches
28 conflicts
0xfa09be5a…1e79
0x34b655…2a6f
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0xfc2493d3…6898
0x34b655…2a6f
10 touches
10 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 conflicts
0xc97150e5…3815
0x851145…3f07
8 touches
6 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
8 touches
6 conflicts
0x41c56387…a8f6
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
28 conflicts on slot 0x623b23c5e7…c53eff
Audit this contract →
← previous block·next block →recent activity