← previous blocknext block →recent activity
Analyzing
Block #99,851,293
29 transactions · 23 stateful · 2026-08-28 08:30:58 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,851,293 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w111w013w014w015w116w117w218w119w021w022w226w128w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cf31547…051b
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0xd58e5c6b…7188
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xfcaee83d…428d
0x34b655…2a6f
4 touches
1 conflict
0xb8dc136f…fb16
0xc8689a…ee79
4 touches
1 conflict
0x15698ac9…2a46
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
3 conflicts on slot 0x3cf315478f…41051b
Audit this contract →
← previous block·next block →recent activity