← previous blocknext block →recent activity

Analyzing

Block #98,062,470

18 transactions · 16 stateful · 2026-08-22 01:32:32 UTC

Parallelism

89/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #98,062,470  ·  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

0x00000000…0007

0x340143…768f

4 touches
1 conflict

0x2bd1c200…56de

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x5d82c9b5…004c

0x3bd359…433a

2 touches
0 conflicts

0xc7ea2751…3347

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0003

0x5afd3e…7620

2 touches
0 conflicts

0x00000000…0004

0x5afd3e…7620

2 touches
0 conflicts

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: 0x34014398…d1768f

1 conflict on slot 0x0000000000…000007

← previous block·next block →recent activity