← previous blocknext block →recent activity

Analyzing

Block #93,344,979

21 transactions · 17 stateful · 2026-08-05 12:18:12 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,344,979  ·  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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xaf8a5557…7093

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xb4e0a934…5fc7

0x34b655…2a6f

6 touches
3 conflicts

0x8b66399b…8d29

0x34b655…2a6f

6 touches
3 conflicts

0x59a54ff4…d21b

0x34b655…2a6f

4 touches
1 conflict

0x5b450c7f…95ee

0x34b655…2a6f

4 touches
1 conflict

0x751f0341…fe9b

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

6 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity