← previous blocknext block →recent activity

Analyzing

Block #100,789,826

23 transactions · 22 stateful · 2026-08-31 15:18:45 UTC

Parallelism

70/100

Blocked

41%

Avg conflicts / tx

1.09

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,789,826  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x11b69a7e…334e

0x01bff4…1071

10 touches
10 conflicts

0x471ced2b…05dc

0x851145…3f07

8 touches
6 conflicts

0x703dea24…d38d

0x34b655…2a6f

6 touches
3 conflicts

0x23529e13…6f25

0x34b655…2a6f

6 touches
3 conflicts

0xa538600d…3da5

0x851145…3f07

4 touches
1 conflict

0x07b86c51…cdae

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

21 conflicts on slot 0xaad6be10ae…2c0801

← previous block·next block →recent activity