← previous blocknext block →recent activity

Analyzing

Block #99,978,433

15 transactions · 14 stateful · 2026-08-28 19:11:44 UTC

Parallelism

80/100

Blocked

57%

Avg conflicts / tx

0.67

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,978,433  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x61571888…b392

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x18e86f02…fa98

0x34b655…2a6f

4 touches
1 conflict

0x35b0198e…3e0d

0x34b655…2a6f

4 touches
1 conflict

0x36126dcb…ca1e

0x34b655…2a6f

4 touches
1 conflict

0x42522e76…2592

0x34b655…2a6f

4 touches
1 conflict

0x4d4389b2…6e07

0x34b655…2a6f

4 touches
1 conflict

0xbb97db90…4c93

0xc8689a…ee79

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 0x6157188898…efb392

← previous block·next block →recent activity