← previous blocknext block →recent activity
Analyzing
Block #99,318,552
18 transactions · 17 stateful · 2026-08-26 11:36:04 UTC
Parallelism
61/100
Blocked
53%
Avg conflicts / tx
1.72
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,318,552 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w06w17w28w210w311w412w514w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xd7443f37…eb79
0x34b655…2a6f
10 touches
10 conflicts
0x3e49348b…9445
0x34b655…2a6f
6 touches
3 conflicts
0x78df73a4…acb6
0x34b655…2a6f
6 touches
3 conflicts
0xac0b4a08…faae
0x34b655…2a6f
6 touches
3 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
4 touches
1 conflict
0x81d64349…50fe
0x34b655…2a6f
4 touches
1 conflict
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity