← previous blocknext block →recent activity
Analyzing
Block #99,953,281
52 transactions · 47 stateful · 2026-08-28 17:05:03 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
2.35
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #99,953,281 · 52 txs across 15 waves · depth 15
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
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w27w08w19w210w313w414w515w616w717w818w919w1021w222w324w426w928w1135w338w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x74e485b1…d380
0x34b655…2a6f
10 touches
10 conflicts
0x7b3a7938…50da
0xd32edf…ff58
9 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x24bb46f7…3853
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
55 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity