← previous blocknext block →recent activity

Analyzing

Block #100,848,494

18 transactions · 15 stateful · 2026-08-31 20:14:07 UTC

Parallelism

83/100

Blocked

13%

Avg conflicts / tx

0.17

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,848,494  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x5c455afd…ce06

0x34b655…2a6f

6 touches
3 conflicts

0x34e6ea13…3aaa

0x34b655…2a6f

4 touches
1 conflict

0x08cc68a2…2a59

0x34b655…2a6f

4 touches
1 conflict

0x9ca6fa7b…aeb3

0x34b655…2a6f

4 touches
1 conflict

0xc17d90ba…5dd7

0x34b655…2a6f

4 touches
1 conflict

0xe720a4c6…8eb0

0x34b655…2a6f

4 touches
1 conflict

0x16586648…476a

0x34b655…2a6f

4 touches
1 conflict

0x53b4ef2b…8a05

0x34b655…2a6f

2 touches
0 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

3 conflicts on slot 0x5c455afdfc…27ce06

← previous block·next block →recent activity