← previous blocknext block →recent activity
Analyzing
Block #99,971,346
25 transactions · 25 stateful · 2026-08-28 18:36:02 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,971,346 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w310w011w112w213w316w417w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc448e273…c274
0x851145…3f07
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x248156cc…9282
0x851145…3f07
8 touches
6 conflicts
0x00000000…003d
0x851145…3f07
8 touches
6 conflicts
0x143cd54f…c109
0x851145…3f07
8 touches
6 conflicts
0x915c095e…c1e5
0x2b46c0…1669
6 touches
3 conflicts
0xcfe06a18…b5b5
0x2b46c0…1669
6 touches
3 conflicts
0xd8fd2add…50fc
0x2b46c0…1669
6 touches
3 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: 0x851145ea…9f3f07
6 conflicts on slot 0xc448e2739c…9cc274
Audit this contract →
← previous block·next block →recent activity