← previous blocknext block →recent activity

Analyzing

Block #93,075,473

15 transactions · 15 stateful · 2026-08-04 13:42:21 UTC

Parallelism

67/100

Blocked

53%

Avg conflicts / tx

0.87

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,075,473  ·  15 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

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x840d3ab7…c8c4

0x34b655…2a6f

8 touches
6 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x36174cc5…a5ef

0x34b655…2a6f

5 touches
3 conflicts

0xce06a0f7…efef

0x34b655…2a6f

5 touches
3 conflicts

0x92339d95…0800

0xb1c8ea…8888

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

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 0x737acb7813…fafce8

← previous block·next block →recent activity