← previous blocknext block →recent activity

Analyzing

Block #102,862,190

19 transactions · 16 stateful · 2026-09-07 21:36:03 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

1.05

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,862,190  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x11b69a7e…334e

0x01bff4…1071

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x002fed35…79fa

0x2a68ba…90c5

10 touches
10 conflicts

0xae8c168c…f519

0x851145…3f07

9 touches
10 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x1d04ae42…3069

0x851145…3f07

4 touches
1 conflict

0x9d1c7ee8…0b73

0x851145…3f07

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: 0x01bff417…bc1071

10 conflicts on slot 0x11b69a7ea1…83334e

← previous block·next block →recent activity