← previous blocknext block →recent activity

Analyzing

Block #99,588,314

20 transactions · 19 stateful · 2026-08-27 10:17:14 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

1.35

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #99,588,314  ·  20 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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x3e6302c8…64f5

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4ac4a2c2…2707

0x34b655…2a6f

4 touches
1 conflict

0x6ede7ba6…a8ca

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xb007c532…74ee

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 0xca841faae5…71486a

← previous block·next block →recent activity