← previous blocknext block →recent activity

Analyzing

Block #100,984,454

18 transactions · 17 stateful · 2026-09-01 07:38:00 UTC

Parallelism

72/100

Blocked

41%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,984,454  ·  18 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

0x54c6fb44…369a

0x34b655…2a6f

10 touches
10 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xf984d8ab…6e4f

0x34b655…2a6f

6 touches
3 conflicts

0xddf09f4e…6b83

0x34b655…2a6f

6 touches
3 conflicts

0xd17580f9…ece1

0x754704…b603

4 touches
1 conflict

0x9ec1d00b…52e6

0x34b655…2a6f

4 touches
1 conflict

0xa9a49465…0424

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

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

10 conflicts on slot 0x54c6fb4487…3b369a

← previous block·next block →recent activity