← previous blocknext block →recent activity

Analyzing

Block #100,749,128

18 transactions · 17 stateful · 2026-08-31 11:53:51 UTC

Parallelism

61/100

Blocked

47%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,749,128  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x191e0467…70e5

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xf2275403…5a98

0x34b655…2a6f

4 touches
1 conflict

0x55192654…91fe

0x34b655…2a6f

4 touches
1 conflict

0x6080eaf8…b5d0

0x34b655…2a6f

4 touches
1 conflict

0x67a56c8b…f955

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

6 conflicts on slot 0x191e0467ba…1470e5

← previous block·next block →recent activity