← previous blocknext block →recent activity

Analyzing

Block #93,663,117

16 transactions · 16 stateful · 2026-08-06 14:57:35 UTC

Parallelism

81/100

Blocked

44%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,663,117  ·  16 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

0xabd0bcfc…64e2

0x34b655…2a6f

6 touches
3 conflicts

0xb7fb89e5…b3c8

0x34b655…2a6f

6 touches
3 conflicts

0x53949d70…0bdd

0x34b655…2a6f

6 touches
3 conflicts

0x5fab7fbe…1ce5

0x34b655…2a6f

4 touches
1 conflict

0x67054426…0a28

0x34b655…2a6f

4 touches
1 conflict

0x731d7308…fd26

0x34b655…2a6f

4 touches
1 conflict

0x74fd0a9b…3aaa

0x34b655…2a6f

4 touches
1 conflict

0x82d510df…8d5c

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

3 conflicts on slot 0xabd0bcfc80…a364e2

← previous block·next block →recent activity