← previous blocknext block →recent activity

Analyzing

Block #94,199,232

24 transactions · 20 stateful · 2026-08-08 11:57:12 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

1.38

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #94,199,232  ·  24 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

0x4cabb80a…46bf

0x34b655…2a6f

16 touches
28 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x8dfb88f5…5592

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x701208a7…46b3

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0xb4f4fd9a…2679

0x34b655…2a6f

4 touches
1 conflict

0xbc96083d…124d

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 0x4cabb80a0e…7546bf

← previous block·next block →recent activity