← previous blocknext block →recent activity

Analyzing

Block #105,841,860

15 transactions · 14 stateful · 2026-09-18 08:19:58 UTC

Parallelism

80/100

Blocked

50%

Avg conflicts / tx

0.67

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #105,841,860  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x272e6316…bbe8

0x34b655…2a6f

6 touches
3 conflicts

0x5684aadd…8d62

0x34b655…2a6f

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0x7c6d6586…833c

0x34b655…2a6f

4 touches
1 conflict

0x7ef9894a…d9e1

0x34b655…2a6f

4 touches
1 conflict

0x8765edd1…a7d5

0x34b655…2a6f

4 touches
1 conflict

0x9068a9bc…86ee

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

3 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity