← previous blocknext block →recent activity

Analyzing

Block #99,180,845

36 transactions · 32 stateful · 2026-08-26 00:03:11 UTC

Parallelism

75/100

Blocked

56%

Avg conflicts / tx

1.44

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #99,180,845  ·  36 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xca841faa…486a

0x34b655…2a6f

18 touches
36 conflicts

0xd97b0449…00a0

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x945d1dbe…e1d7

0xc8689a…ee79

6 touches
3 conflicts

0x35cca7f9…79d6

0x34b655…2a6f

4 touches
1 conflict

0x36cc2d85…e260

0x34b655…2a6f

4 touches
1 conflict

0x6f6fc26c…3e34

0x34b655…2a6f

4 touches
1 conflict

0x70ace55b…8c81

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

36 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity