← previous blocknext block →recent activity

Analyzing

Block #96,708,644

18 transactions · 15 stateful · 2026-08-17 06:49:17 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #96,708,644  ·  18 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

0x00000000…0002

0x103de0…bb55

6 touches
3 conflicts

0xd676e291…3ecf

0x34b655…2a6f

6 touches
3 conflicts

0x9fbf0630…ae97

0x34b655…2a6f

4 touches
1 conflict

0xbb96f8af…205f

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x8cd684d0…c3cb

0x34b655…2a6f

4 touches
1 conflict

0x45505116…3285

0xd32edf…ff58

3 touches
1 conflict

0xba5743c7…21c0

0x1b6862…e19c

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: 0x103de0b5…25bb55

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity