← previous blocknext block →recent activity

Analyzing

Block #95,783,844

21 transactions · 19 stateful · 2026-08-14 01:17:02 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,783,844  ·  21 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

0x734ee320…caae

0x34b655…2a6f

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x59164e7a…7e0a

0x34b655…2a6f

6 touches
3 conflicts

0x002fed35…79fa

0x2a68ba…90c5

4 touches
1 conflict

0xe1f266d8…6836

0x065c9d…c394

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xbf99cee5…73cd

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 0x734ee32053…cecaae

← previous block·next block →recent activity