← previous blocknext block →recent activity

Analyzing

Block #100,617,154

22 transactions · 22 stateful · 2026-08-31 00:49:59 UTC

Parallelism

59/100

Blocked

41%

Avg conflicts / tx

0.82

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #100,617,154  ·  22 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

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x1a3d2527…8ca0

0x34b655…2a6f

4 touches
1 conflict

0x8db32935…81a7

0x34b655…2a6f

4 touches
1 conflict

0xb0f5d668…99ac

0x34b655…2a6f

4 touches
1 conflict

0xe9457301…83cd

0x34b655…2a6f

4 touches
1 conflict

0xf79df061…e005

0xe52b14…7230

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity