← previous blocknext block →recent activity

Analyzing

Block #98,501,503

20 transactions · 19 stateful · 2026-08-23 14:23:00 UTC

Parallelism

75/100

Blocked

37%

Avg conflicts / tx

0.45

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #98,501,503  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0xc0b1105a…3936

0x065c9d…c394

4 touches
1 conflict

0x49b0842d…0a93

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xbb3f3c…e046

4 touches
1 conflict

0x0f8965bb…e238

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: Market-MON/USDC

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity