← previous blocknext block →recent activity

Analyzing

Block #96,543,330

20 transactions · 19 stateful · 2026-08-16 16:57:50 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

0.95

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #96,543,330  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xec7d120d…7084

0x34b655…2a6f

8 touches
6 conflicts

0xf0d45ffd…89cf

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x53f393fa…00b9

0x34b655…2a6f

4 touches
1 conflict

0x5a0a2b03…ac50

0x34b655…2a6f

4 touches
1 conflict

0x6f900be0…cd6e

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x745a7fd6…5fea

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 0xec7d120df9…5d7084

← previous block·next block →recent activity