← previous blocknext block →recent activity

Analyzing

Block #100,228,501

19 transactions · 18 stateful · 2026-08-29 16:10:50 UTC

Parallelism

53/100

Blocked

50%

Avg conflicts / tx

1.47

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #100,228,501  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xb409e204…89ac

0x34b655…2a6f

6 touches
3 conflicts

0xdfce7dfe…5053

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x2c0c3e3f…5849

0x34b655…2a6f

4 touches
1 conflict

0xb62f3e28…8ceb

0x34b655…2a6f

4 touches
1 conflict

0xd66696e0…0842

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity