← previous blocknext block →recent activity

Analyzing

Block #93,682,462

21 transactions · 20 stateful · 2026-08-06 16:34:50 UTC

Parallelism

62/100

Blocked

55%

Avg conflicts / tx

1.43

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #93,682,462  ·  21 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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0xbbeac3b7…c14b

0x34b655…2a6f

6 touches
3 conflicts

0xb5681617…e980

0x34b655…2a6f

6 touches
3 conflicts

0x4c702894…9f4c

0x34b655…2a6f

6 touches
3 conflicts

0x6ddc75c8…c0e4

0x34b655…2a6f

4 touches
1 conflict

0x6e6b8ec7…2197

0x34b655…2a6f

4 touches
1 conflict

0x74137b07…5880

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity