← previous blocknext block →recent activity

Analyzing

Block #95,716,098

24 transactions · 21 stateful · 2026-08-13 19:36:18 UTC

Parallelism

71/100

Blocked

48%

Avg conflicts / tx

0.83

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,716,098  ·  24 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

0xe2ca9bf2…8da8

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0xafb8e71e…9285

0x34b655…2a6f

6 touches
3 conflicts

0xa4c56761…79e0

0x34b655…2a6f

4 touches
1 conflict

0x5484fc7f…a8d8

0x34b655…2a6f

4 touches
1 conflict

0xbfbbf561…0976

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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 0xe2ca9bf21a…2c8da8

← previous block·next block →recent activity