← previous blocknext block →recent activity
Analyzing
Block #99,198,110
44 transactions · 35 stateful · 2026-08-26 01:30:04 UTC
Parallelism
84/100
Blocked
51%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,198,110 · 44 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
4w05w113w014w115w016w117w218w319w428w129w431w532w533w634w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x40c49f…2af0
12 touches
15 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x348fda08…7e96
0x065c9d…c394
8 touches
6 conflicts
0x065ff70b…356d
0x40c49f…2af0
8 touches
6 conflicts
0xe80f7fab…74bd
0x40c49f…2af0
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity