← previous blocknext block →recent activity

Analyzing

Block #96,136,167

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

Parallelism

59/100

Blocked

65%

Avg conflicts / tx

1.88

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #96,136,167  ·  17 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

0x53f393fa…00b9

0x34b655…2a6f

12 touches
15 conflicts

0x424934c8…f2f1

0x34b655…2a6f

10 touches
10 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xf5ea108a…dbf6

0x34b655…2a6f

4 touches
1 conflict

0x158becdc…73ed

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xd7e54f60…8bd3

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

15 conflicts on slot 0x53f393fafd…2a00b9

← previous block·next block →recent activity