← previous blocknext block →recent activity

Analyzing

Block #99,486,792

21 transactions · 21 stateful · 2026-08-27 01:43:15 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,486,792  ·  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

0x8b7fe709…9d99

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x04a53fbd…0ac5

0x34b655…2a6f

10 touches
10 conflicts

0x7a86be7d…71c6

0x34b655…2a6f

6 touches
3 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0xc7a73c18…0ac6

0x34b655…2a6f

6 touches
3 conflicts

0x953517cb…cdec

0x34b655…2a6f

6 touches
3 conflicts

0xeaced15b…2221

0x754704…b603

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

15 conflicts on slot 0x8b7fe70996…af9d99

← previous block·next block →recent activity