← previous blocknext block →recent activity
Analyzing
Block #99,318,066
14 transactions · 14 stateful · 2026-08-26 11:33:37 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,318,066 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w08w09w110w211w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb32e068b…6e1a
0x34b655…2a6f
6 touches
3 conflicts
0xc10b903d…2f54
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x961c0cd9…0937
0x34b655…2a6f
4 touches
1 conflict
0xc8525006…2b45
0x2b46c0…1669
2 touches
0 conflicts
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 0xb32e068b05…db6e1a
Audit this contract →
← previous block·next block →recent activity