← previous blocknext block →recent activity

Analyzing

Block #95,656,498

23 transactions · 20 stateful · 2026-08-13 14:35:30 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

1.09

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,656,498  ·  23 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

0x00000000…0031

0x59df86…2780

12 touches
15 conflicts

0x43fd3667…094b

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0x5e1b6ade…542d

0x34b655…2a6f

4 touches
1 conflict

0x2840c278…bbc7

0x34b655…2a6f

4 touches
1 conflict

0xf18fa6c1…4bf8

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: 0x59df8637…6d2780

15 conflicts on slot 0x0000000000…000031

← previous block·next block →recent activity