← previous blocknext block →recent activity
Analyzing
Block #99,330,839
47 transactions · 40 stateful · 2026-08-26 12:37:52 UTC
Parallelism
77/100
Blocked
68%
Avg conflicts / tx
1.66
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #99,330,839 · 47 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w08w110w013w114w015w116w217w020w021w122w323w124w125w326w227w128w230w431w532w640w443w744w846w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
10 touches
10 conflicts
0x3e49348b…9445
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0x74c38383…2a82
0xd32edf…ff58
7 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity