← previous blocknext block →recent activity

Analyzing

Block #100,456,181

18 transactions · 18 stateful · 2026-08-30 11:20:11 UTC

Parallelism

89/100

Blocked

22%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #100,456,181  ·  18 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x009a0451…b83e

0x34b655…2a6f

4 touches
1 conflict

0x26471102…35f9

0x34b655…2a6f

4 touches
1 conflict

0x45f2035a…1803

0x34b655…2a6f

4 touches
1 conflict

0x517cc930…5f1e

0x34b655…2a6f

4 touches
1 conflict

0x5b37bb6b…aaff

0x34b655…2a6f

4 touches
1 conflict

0x5b37bb6b…ab00

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

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

1 conflict on slot 0x889d5e90c7…59929a

← previous block·next block →recent activity