← previous blocknext block →recent activity

Analyzing

Block #99,480,788

20 transactions · 19 stateful · 2026-08-27 01:13:01 UTC

Parallelism

45/100

Blocked

53%

Avg conflicts / tx

2.65

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #99,480,788  ·  20 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xd814f518…f5b4

0x34b655…2a6f

20 touches
45 conflicts

0x0168baa0…940f

0x34b655…2a6f

16 touches
28 conflicts

0xec3a63b4…29ce

0x34b655…2a6f

12 touches
15 conflicts

0x64275949…d698

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0xf6deafb5…5c25

0x34b655…2a6f

6 touches
3 conflicts

0x044844a0…7418

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

45 conflicts on slot 0xd814f51828…c6f5b4

← previous block·next block →recent activity