← previous blocknext block →recent activity
Analyzing
Block #99,873,591
22 transactions · 21 stateful · 2026-08-28 10:23:26 UTC
Parallelism
77/100
Blocked
43%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,873,591 · 22 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
1w02w14w28w010w111w212w313w414w015w117w121w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e935e5f…fcd7
0x34b655…2a6f
10 touches
10 conflicts
0xbad4e90b…33a5
0x34b655…2a6f
8 touches
6 conflicts
0x6a5ca890…05c7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x6183ee9a…21b1
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
10 conflicts on slot 0x4e935e5f3a…2afcd7
Audit this contract →
← previous block·next block →recent activity