← previous blocknext block →recent activity

Analyzing

Block #99,937,384

18 transactions · 16 stateful · 2026-08-28 15:44:55 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

0.83

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,937,384  ·  18 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xbd22d0fc…64fd

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x2c9d2f48…8fc2

0x34b655…2a6f

2 touches
0 conflicts

0x31899aa5…ab0d

0x34b655…2a6f

2 touches
0 conflicts

0x359866c7…de7b

0x34b655…2a6f

2 touches
0 conflicts

0x4c9a9f2e…09f3

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