← previous blocknext block →recent activity

Analyzing

Block #95,206,314

16 transactions · 14 stateful · 2026-08-12 00:37:34 UTC

Parallelism

50/100

Blocked

71%

Avg conflicts / tx

2.13

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #95,206,314  ·  16 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x6518075e…2b17

0x2a68ba…90c5

14 touches
21 conflicts

0xa1087a5c…66c4

0x754704…b603

14 touches
21 conflicts

0x2b54cadb…4425

0xd18b7e…414b

14 touches
21 conflicts

0x4f4fef48…33a0

0x40c49f…2af0

13 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xda366b17…f884

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

21 conflicts on slot 0x6518075e89…5f2b17

← previous block·next block →recent activity