← previous blocknext block →recent activity

Analyzing

Block #108,463,030

22 transactions · 20 stateful · 2026-09-27 12:17:11 UTC

Parallelism

68/100

Blocked

40%

Avg conflicts / tx

1.09

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #108,463,030  ·  22 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

0x00000000…0002

0x125f12…a50b

12 touches
15 conflicts

0x3a7ae099…026e

0xd32edf…ff58

9 touches
10 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001c

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0009

0x125f12…a50b

6 touches
3 conflicts

0x5f77d607…2c84

0x065c9d…c394

4 touches
1 conflict

0x892daf6e…48d8

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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: 0x125f12a1…cda50b

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity