← previous blocknext block →recent activity
Analyzing
Block #99,660,254
25 transactions · 23 stateful · 2026-08-27 16:23:35 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,660,254 · 25 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
2w03w14w25w36w17w08w29w310w215w016w117w120w022w124w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25bd380f…a658
0x34b655…2a6f
8 touches
6 conflicts
0x8ba177d5…0baf
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x8d47c9a4…f11e
0x1b6862…e19c
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 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
6 conflicts on slot 0x25bd380fc0…1ea658
Audit this contract →
← previous block·next block →recent activity