← previous blocknext block →recent activity

Analyzing

Block #100,920,683

22 transactions · 21 stateful · 2026-09-01 02:17:13 UTC

Parallelism

82/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,920,683  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xe4978fe2…7b9b

0x34b655…2a6f

6 touches
3 conflicts

0x1db5837f…1264

0x34b655…2a6f

6 touches
3 conflicts

0x2827ae77…4368

0x34b655…2a6f

6 touches
3 conflicts

0x91cdfdeb…7feb

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…002d

0x1b6862…e19c

4 touches
1 conflict

0xac79a0c7…be14

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x0fcb1428…3534

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

3 conflicts on slot 0xe4978fe2a3…037b9b

← previous block·next block →recent activity