← previous blocknext block →recent activity

Analyzing

Block #93,237,829

21 transactions · 15 stateful · 2026-08-05 03:19:28 UTC

Parallelism

76/100

Blocked

53%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,237,829  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x61681cb3…aa6d

0x34b655…2a6f

6 touches
3 conflicts

0x026c16fd…2dcb

0xd32edf…ff58

5 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5da59c2b…d7b2

0x34b655…2a6f

4 touches
1 conflict

0xac3e4969…39e9

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xe283e878…7262

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 0x61681cb311…b0aa6d

← previous block·next block →recent activity