← previous blocknext block →recent activity

Analyzing

Block #96,116,160

16 transactions · 14 stateful · 2026-08-15 05:09:00 UTC

Parallelism

75/100

Blocked

43%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #96,116,160  ·  16 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x9e10b712…1fc2

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xc782ec05…5bb2

0xa6afd3…d132

6 touches
3 conflicts

0x4cabb80a…46bf

0x34b655…2a6f

4 touches
1 conflict

0x53f393fa…00b9

0x34b655…2a6f

4 touches
1 conflict

0x8ec95f2b…f4d7

0x34b655…2a6f

4 touches
1 conflict

0xa4e9800f…4ab0

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 0x9e10b71208…5e1fc2

← previous block·next block →recent activity