← previous blocknext block →recent activity

Analyzing

Block #96,150,985

20 transactions · 16 stateful · 2026-08-15 08:04:13 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #96,150,985  ·  20 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

0x4c188934…158e

0x34b655…2a6f

8 touches
6 conflicts

0xa2c9330e…e167

0x34b655…2a6f

6 touches
3 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

6 touches
3 conflicts

0xe2addb64…3da9

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x6b17f7a0…af41

0x34b655…2a6f

4 touches
1 conflict

0x862ac33e…15a3

0x34b655…2a6f

4 touches
1 conflict

0x95ea33cc…0339

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 0x4c18893450…c5158e

← previous block·next block →recent activity