← previous blocknext block →recent activity

Analyzing

Block #96,637,090

36 transactions · 31 stateful · 2026-08-17 00:49:24 UTC

Parallelism

67/100

Blocked

68%

Avg conflicts / tx

1.94

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #96,637,090  ·  36 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xec7d120d…7084

0x34b655…2a6f

14 touches
21 conflicts

0x8252706a…7ca5

0x34b655…2a6f

12 touches
15 conflicts

0x2d651956…12e8

0x34b655…2a6f

8 touches
6 conflicts

0x4acbdbcf…a8c6

0x34b655…2a6f

8 touches
6 conflicts

0xa3a621f8…75a2

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0x103de0…bb55

6 touches
3 conflicts

0x5c5238c6…f2dc

0x34b655…2a6f

6 touches
3 conflicts

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

21 conflicts on slot 0xec7d120df9…5d7084

← previous block·next block →recent activity