← previous blocknext block →recent activity

Analyzing

Block #92,755,963

18 transactions · 16 stateful · 2026-08-03 10:54:04 UTC

Parallelism

89/100

Blocked

31%

Avg conflicts / tx

0.28

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #92,755,963  ·  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

0x42041fec…bd86

0x754704…b603

4 touches
1 conflict

0x0e37797c…d724

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0xac2a0273…721b

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