← previous blocknext block →recent activity

Analyzing

Block #95,350,375

19 transactions · 18 stateful · 2026-08-12 12:53:20 UTC

Parallelism

68/100

Blocked

56%

Avg conflicts / tx

1.16

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,350,375  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0x95c47f03…f1bb

0x34b655…2a6f

6 touches
3 conflicts

0xd676e291…3ecf

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0x93b6fab0…09d6

0x34b655…2a6f

6 touches
3 conflicts

0x25191452…d2ed

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35d

0x34b655…2a6f

4 touches
1 conflict

0x5fab7fbe…1ce5

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

3 conflicts on slot 0xb3fb9fb561…7664db

← previous block·next block →recent activity