← previous blocknext block →recent activity

Analyzing

Block #99,953,908

22 transactions · 22 stateful · 2026-08-28 17:08:13 UTC

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

1.5

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #99,953,908  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xca841faa…486a

0x34b655…2a6f

16 touches
28 conflicts

0xb240b520…a88a

0x34b655…2a6f

6 touches
3 conflicts

0x5fad6fee…7714

0x34b655…2a6f

4 touches
1 conflict

0x64285c07…1fad

0x34b655…2a6f

4 touches
1 conflict

0x775a8ad3…8307

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x8765edd1…a7d5

0x34b655…2a6f

4 touches
1 conflict

0x96ed54e2…04ed

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: Perpl

28 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity