← previous blocknext block →recent activity

Analyzing

Block #102,874,541

18 transactions · 16 stateful · 2026-09-07 22:38:12 UTC

Parallelism

72/100

Blocked

50%

Avg conflicts / tx

0.83

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,874,541  ·  18 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x5c455afd…ce06

0x34b655…2a6f

4 touches
1 conflict

0x6aeb45e9…c0f2

0x34b655…2a6f

4 touches
1 conflict

0x6e5bf2da…a3c3

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x820d7282…6c34

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

← previous block·next block →recent activity