← previous blocknext block →recent activity

Analyzing

Block #100,162,590

27 transactions · 25 stateful · 2026-08-29 10:39:04 UTC

Parallelism

56/100

Blocked

48%

Avg conflicts / tx

1.33

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #100,162,590  ·  27 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xd2a76d80…ee44

0x34b655…2a6f

10 touches
10 conflicts

0xa801295f…7de6

0x34b655…2a6f

8 touches
6 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0x191e0467…70e5

0x34b655…2a6f

6 touches
3 conflicts

0x85bfd0af…ce96

0x34b655…2a6f

6 touches
3 conflicts

0xca608d0c…f23b

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity