← previous blocknext block →recent activity

Analyzing

Block #106,185,825

19 transactions · 19 stateful · 2026-09-19 13:12:15 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.84

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #106,185,825  ·  19 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

0xf2acfba1…5e29

0x34b655…2a6f

10 touches
10 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0xb5c7c6aa…fdba

0x34b655…2a6f

4 touches
1 conflict

0x67a56c8b…f955

0x34b655…2a6f

4 touches
1 conflict

0x35b89cd8…5092

0x34b655…2a6f

4 touches
1 conflict

0xd41f5136…97c6

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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 0xf2acfba1cf…a85e29

← previous block·next block →recent activity