← previous blocknext block →recent activity

Analyzing

Block #100,588,493

19 transactions · 19 stateful · 2026-08-30 22:25:48 UTC

Parallelism

74/100

Blocked

37%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,588,493  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x51a38849…7382

0x34b655…2a6f

4 touches
1 conflict

0x59a133dd…7982

0x34b655…2a6f

4 touches
1 conflict

0x691d7bbd…bdbf

0x34b655…2a6f

4 touches
1 conflict

0x6ea13ae5…72d1

0x34b655…2a6f

4 touches
1 conflict

0x76622fb2…4f08

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity