← previous blocknext block →recent activity

Analyzing

Block #99,872,580

20 transactions · 19 stateful · 2026-08-28 10:18:21 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

0.8

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,872,580  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x40c49f…2af0

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xd1203697…1ae0

0x40c49f…2af0

6 touches
3 conflicts

0x70f69477…a1b9

0x40c49f…2af0

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x0d03bddb…6658

0x34b655…2a6f

4 touches
1 conflict

0x470b41f6…fc68

0x34b655…2a6f

4 touches
1 conflict

0xbad4e90b…33a5

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: 0x40c49f17…d22af0

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity