← previous blocknext block →recent activity

Analyzing

Block #99,273,213

23 transactions · 20 stateful · 2026-08-26 07:48:00 UTC

Parallelism

78/100

Blocked

35%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,273,213  ·  23 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…0002

0xf5b5f7…6d70

10 touches
10 conflicts

0x631b4113…baa9

0x34b655…2a6f

4 touches
1 conflict

0xf4b2a427…0234

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0304f632…1f73

0x34b655…2a6f

2 touches
0 conflicts

0x032caa9b…dca8

0x34b655…2a6f

2 touches
0 conflicts

0x2b6e2a61…3dae

0x34b655…2a6f

2 touches
0 conflicts

0x37c0660b…e0bf

0x34b655…2a6f

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: 0xf5b5f7f8…a36d70

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity