← previous blocknext block →recent activity

Analyzing

Block #93,664,612

19 transactions · 17 stateful · 2026-08-06 15:05:06 UTC

Parallelism

53/100

Blocked

59%

Avg conflicts / tx

1.11

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #93,664,612  ·  19 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x310afe2c…83e1

0x34b655…2a6f

8 touches
6 conflicts

0x1bf8d2af…d140

0x34b655…2a6f

8 touches
6 conflicts

0xc5dc29f0…f0c6

0x34b655…2a6f

6 touches
3 conflicts

0x40837ad3…1345

0x34b655…2a6f

6 touches
3 conflicts

0xcc351d6d…256b

0x34b655…2a6f

6 touches
3 conflicts

0x98212952…9ba6

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f1

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity