← previous blocknext block →recent activity

Analyzing

Block #93,362,525

20 transactions · 18 stateful · 2026-08-05 13:46:26 UTC

Parallelism

70/100

Blocked

50%

Avg conflicts / tx

1.05

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #93,362,525  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xafe6567a…4f0a

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xd66696e0…0842

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xac3e4969…39e9

0x34b655…2a6f

8 touches
6 conflicts

0xd895ee0b…d301

0x34b655…2a6f

6 touches
3 conflicts

0x9cf9008a…d826

0x34b655…2a6f

4 touches
1 conflict

0xa8488658…af8b

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 0xafe6567a48…8e4f0a

← previous block·next block →recent activity