← previous blocknext block →recent activity

Analyzing

Block #100,108,637

19 transactions · 17 stateful · 2026-08-29 06:07:16 UTC

Parallelism

63/100

Blocked

47%

Avg conflicts / tx

0.89

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,108,637  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x45c2d5b4…3e8f

0x34b655…2a6f

6 touches
3 conflicts

0xe283e878…7262

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xa11b60f7…8e8b

0x34b655…2a6f

4 touches
1 conflict

0xa8d49a93…42c7

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 0x92385428ad…dc6941

← previous block·next block →recent activity