← previous blocknext block →recent activity

Analyzing

Block #99,994,082

19 transactions · 18 stateful · 2026-08-28 20:30:35 UTC

Parallelism

74/100

Blocked

44%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,994,082  ·  19 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x7bef9f87…a533

0x34b655…2a6f

10 touches
10 conflicts

0xf6deafb5…5c25

0x34b655…2a6f

10 touches
10 conflicts

0x932a9590…0b19

0x34b655…2a6f

6 touches
3 conflicts

0xac9e0b10…4f67

0x34b655…2a6f

6 touches
3 conflicts

0x2d3930d3…c9b8

0x34b655…2a6f

4 touches
1 conflict

0x42522e76…2592

0x34b655…2a6f

4 touches
1 conflict

0x530209ce…2a1b

0x34b655…2a6f

4 touches
1 conflict

0x6dedaff6…161b

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 0x7bef9f87bb…a7a533

← previous block·next block →recent activity