← previous blocknext block →recent activity

Analyzing

Block #102,810,043

16 transactions · 15 stateful · 2026-09-07 17:13:33 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,810,043  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xa605468c…1bfc

0x34ae4d…3fc5

4 touches
1 conflict

0x51cfbcbc…fa29

0x34b655…2a6f

4 touches
1 conflict

0x56828d99…6126

0x34b655…2a6f

4 touches
1 conflict

0x886db264…846e

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

← previous block·next block →recent activity