← previous blocknext block →recent activity
Analyzing
Block #98,843,002
20 transactions · 20 stateful · 2026-08-24 19:36:47 UTC
Parallelism
65/100
Blocked
45%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,843,002 · 20 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
1w02w13w05w18w010w011w112w214w015w216w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0036
0x35a73b…6042
6 touches
3 conflicts
0xaf831072…51d5
0x69a5f9…2fef
6 touches
3 conflicts
0xaf831072…51d6
0x69a5f9…2fef
6 touches
3 conflicts
0xaf831072…51dc
0x69a5f9…2fef
6 touches
3 conflicts
0x2ef1d89b…196d
0x754704…b603
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity