← previous blocknext block →recent activity

Analyzing

Block #96,640,444

17 transactions · 17 stateful · 2026-08-17 01:06:17 UTC

Parallelism

71/100

Blocked

41%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,640,444  ·  17 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

0xf0d45ffd…89cf

0x34b655…2a6f

8 touches
6 conflicts

0x83220a94…1bd7

0x34b655…2a6f

6 touches
3 conflicts

0x9a3463f0…0b73

0x34b655…2a6f

6 touches
3 conflicts

0xea1b8c07…b969

0x34b655…2a6f

6 touches
3 conflicts

0x48532ab5…d4c1

0x34b655…2a6f

4 touches
1 conflict

0x48532ab5…d4c2

0x34b655…2a6f

4 touches
1 conflict

0x4acc6dca…a868

0x34b655…2a6f

4 touches
1 conflict

0x6bdb9869…7558

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

6 conflicts on slot 0xf0d45ffdb0…4089cf

← previous block·next block →recent activity