← previous blocknext block →recent activity

Analyzing

Block #93,483,556

20 transactions · 18 stateful · 2026-08-05 23:54:55 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,483,556  ·  20 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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc6b9bb4b…145a

0x34b655…2a6f

8 touches
6 conflicts

0x50dbe610…177f

0x34b655…2a6f

6 touches
3 conflicts

0xe4af4c87…9964

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x2b54cadb…4425

0xd18b7e…414b

4 touches
1 conflict

0x17a14264…f419

0x34b655…2a6f

4 touches
1 conflict

0x31b39922…1e65

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 0x482471adbb…39122f

← previous block·next block →recent activity