← previous blocknext block →recent activity

Analyzing

Block #100,748,918

22 transactions · 19 stateful · 2026-08-31 11:52:47 UTC

Parallelism

77/100

Blocked

47%

Avg conflicts / tx

0.82

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,748,918  ·  22 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

0xaad6be10…0801

0x2a68ba…90c5

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xfac62062…b38c

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x1d9154e7…8821

0x34b655…2a6f

6 touches
3 conflicts

0x3a5f4dea…0443

0x851145…3f07

4 touches
1 conflict

0xb841b014…152c

0x065c9d…c394

4 touches
1 conflict

0x002fed35…79fa

0x2a68ba…90c5

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

10 conflicts on slot 0xaad6be10ae…2c0801

← previous block·next block →recent activity