← previous blocknext block →recent activity

Analyzing

Block #95,748,698

17 transactions · 16 stateful · 2026-08-13 22:20:17 UTC

Parallelism

59/100

Blocked

63%

Avg conflicts / tx

1.47

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,748,698  ·  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

0xf0d45ffd…89cf

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x0a57a2b8…3cdd

0x34b655…2a6f

6 touches
3 conflicts

0x66d5e476…8a1f

0x34b655…2a6f

6 touches
3 conflicts

0x3a2b650f…f454

0x34b655…2a6f

4 touches
1 conflict

0x3f25409b…f92b

0x34b655…2a6f

4 touches
1 conflict

0x736bfd85…2594

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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

10 conflicts on slot 0xf0d45ffdb0…4089cf

← previous block·next block →recent activity