← previous blocknext block →recent activity
Analyzing
Block #100,740,699
25 transactions · 23 stateful · 2026-08-31 11:11:27 UTC
Parallelism
64/100
Blocked
78%
Avg conflicts / tx
2.16
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,740,699 · 25 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
1w02w13w24w35w47w111w412w413w514w615w716w817w218w319w522w524w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0xf3d10975…0d07
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0xaa2e91af…76f1
0xd32edf…ff58
11 touches
15 conflicts
0x2c084486…20a6
0x851145…3f07
10 touches
10 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
10 touches
10 conflicts
0x11b69a7e…334e
0x01bff4…1071
10 touches
10 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
15 conflicts on slot 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity