← previous blocknext block →recent activity

Analyzing

Block #101,658,989

17 transactions · 16 stateful · 2026-09-03 16:12:04 UTC

Parallelism

47/100

Blocked

63%

Avg conflicts / tx

1.53

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #101,658,989  ·  17 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xb957a72e…fe46

0x34b655…2a6f

6 touches
3 conflicts

0x9b4f173c…94e6

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0x85664e9e…a762

0x34b655…2a6f

5 touches
3 conflicts

0x77c6a6c8…14f9

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity