← previous blocknext block →recent activity

Analyzing

Block #98,014,702

20 transactions · 19 stateful · 2026-08-21 21:32:02 UTC

Parallelism

85/100

Blocked

21%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,014,702  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x3f81bcfb…2905

0x40c49f…2af0

4 touches
1 conflict

0xee757899…302b

0x34b655…2a6f

4 touches
1 conflict

0xfe2bac2b…2cec

0x065c9d…c394

4 touches
1 conflict

0xdf352747…7eaf

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0007

0x340143…768f

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity