← previous blocknext block →recent activity

Analyzing

Block #99,187,391

18 transactions · 18 stateful · 2026-08-26 00:36:08 UTC

Parallelism

72/100

Blocked

50%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,187,391  ·  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

0x27b6010e…e4aa

0x34b655…2a6f

6 touches
3 conflicts

0x67f0ccf9…20ed

0x34b655…2a6f

6 touches
3 conflicts

0xd97b0449…00a0

0x34b655…2a6f

6 touches
3 conflicts

0x2ed57966…f7b9

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001a

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002a

0x1b6862…e19c

4 touches
1 conflict

0x0f94ee4c…1899

0x1b6862…e19c

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

3 conflicts on slot 0x27b6010e94…34e4aa

← previous block·next block →recent activity