← previous blocknext block →recent activity
Analyzing
Block #98,507,946
29 transactions · 23 stateful · 2026-08-23 14:56:27 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.52
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,507,946 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w07w18w010w014w116w317w418w119w522w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6be58ee5…4502
0x34b655…2a6f
8 touches
6 conflicts
0x065ff70b…356d
0x40c49f…2af0
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x8ff85b19…dde0
0x34b655…2a6f
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
6 conflicts on slot 0x6be58ee5c9…874502
Audit this contract →
← previous block·next block →recent activity