← previous blocknext block →recent activity
Analyzing
Block #99,481,707
21 transactions · 21 stateful · 2026-08-27 01:17:38 UTC
Parallelism
76/100
Blocked
57%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,481,707 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w07w08w19w110w211w014w315w116w118w319w420w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd22d0fc…64fd
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x065ff70b…356d
0x40c49f…2af0
6 touches
3 conflicts
0x9a0d2c8b…845b
0x40c49f…2af0
4 touches
2 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
4 touches
1 conflict
0xe49b1b9b…0be1
0x2b46c0…1669
4 touches
1 conflict
0x737acb78…fce8
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 0xbd22d0fc04…0464fd
Audit this contract →
← previous block·next block →recent activity