← previous blocknext block →recent activity
Analyzing
Block #99,354,364
31 transactions · 27 stateful · 2026-08-26 14:36:15 UTC
Parallelism
68/100
Blocked
70%
Avg conflicts / tx
1.84
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,354,364 · 31 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w17w08w19w210w311w412w513w614w719w222w823w924w226w128w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0xd3c05624…3417
0x34b655…2a6f
10 touches
10 conflicts
0x8429e394…b13d
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x73912233…4587
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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: Perpl
28 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity