← previous blocknext block →recent activity
Analyzing
Block #99,606,562
75 transactions · 59 stateful · 2026-08-27 11:51:09 UTC
Parallelism
76/100
Blocked
80%
Avg conflicts / tx
3.71
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #99,606,562 · 75 txs across 18 waves · depth 18
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
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w37w48w59w610w713w114w115w216w317w418w550w851w961w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
36 touches
153 conflicts
0x889d5e90…929a
0x2a68ba…90c5
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xd1203697…1ae0
0x40c49f…2af0
16 touches
28 conflicts
0x6eff310a…c34c
0x2b46c0…1669
14 touches
21 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
14 touches
21 conflicts
0xe49b1b9b…0be1
0x2b46c0…1669
14 touches
21 conflicts
0x46279ae7…20dd
0x2b46c0…1669
14 touches
21 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: 0xf5b5f7f8…a36d70
153 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity