← previous blocknext block →recent activity

Analyzing

Block #102,860,755

31 transactions · 28 stateful · 2026-09-07 21:28:50 UTC

Parallelism

68/100

Blocked

64%

Avg conflicts / tx

1.55

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #102,860,755  ·  31 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xaad6be10…0801

0x2a68ba…90c5

12 touches
15 conflicts

0x11b69a7e…334e

0x01bff4…1071

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xd17580f9…ece1

0x754704…b603

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

8 touches
6 conflicts

0xb686e6f5…f6d1

0xc8689a…ee79

6 touches
3 conflicts

0x443a3e47…f4a4

0x065c9d…c394

6 touches
3 conflicts

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: Kuru Exchange: MarginAccount

15 conflicts on slot 0xaad6be10ae…2c0801

← previous block·next block →recent activity