← previous blocknext block →recent activity

Analyzing

Block #94,901,386

19 transactions · 19 stateful · 2026-08-10 23:02:59 UTC

Parallelism

63/100

Blocked

58%

Avg conflicts / tx

1.42

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #94,901,386  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x0a57a2b8…3cdd

0x34b655…2a6f

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x11b69a7e…334e

0x01bff4…1071

8 touches
6 conflicts

0x002fed35…79fa

0x2a68ba…90c5

8 touches
6 conflicts

0x94a77fc9…7577

0x34b655…2a6f

6 touches
3 conflicts

0x4c202f65…ff77

0x851145…3f07

6 touches
3 conflicts

0x8c7321a1…a72d

0x34b655…2a6f

4 touches
1 conflict

0x0edf889a…ce9d

0x01bff4…1071

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

15 conflicts on slot 0x0a57a2b8cd…773cdd

← previous block·next block →recent activity