← previous blocknext block →recent activity

Analyzing

Block #100,977,101

17 transactions · 16 stateful · 2026-09-01 07:01:01 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

1.12

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,977,101  ·  17 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

0x737acb78…fce8

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0xd17580f9…ece1

0x754704…b603

8 touches
6 conflicts

0x9c6a9da2…c628

0x34b655…2a6f

6 touches
3 conflicts

0x642ddc4f…699d

0x34b655…2a6f

4 touches
1 conflict

0x2f358e74…1022

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xde54926c…1c87

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 0x737acb7813…fafce8

← previous block·next block →recent activity