← previous blocknext block →recent activity

Analyzing

Block #100,813,341

20 transactions · 20 stateful · 2026-08-31 17:17:05 UTC

Parallelism

70/100

Blocked

35%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,813,341  ·  20 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

0x07b86c51…cdae

0x2a68ba…90c5

12 touches
15 conflicts

0xd393ebc1…ebc5

0x851145…3f07

11 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x11b69a7e…334e

0x01bff4…1071

10 touches
10 conflicts

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xa952c504…7b64

0x34b655…2a6f

4 touches
1 conflict

0x175d5d2e…6c79

0x34b655…2a6f

2 touches
0 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 0x07b86c515d…73cdae

← previous block·next block →recent activity