← previous blocknext block →recent activity

Analyzing

Block #94,197,118

7 transactions · 7 stateful · 2026-08-08 11:46:30 UTC

Parallelism

57/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #94,197,118  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xe283e878…7262

0x34b655…2a6f

4 touches
1 conflict

0x05527801…9c11

0x34b655…2a6f

2 touches
0 conflicts

0x0680b73d…71b7

0x34b655…2a6f

2 touches
0 conflicts

0x167dc8aa…d65e

0x34b655…2a6f

2 touches
0 conflicts

0x17f2c132…ca5f

0x34b655…2a6f

2 touches
0 conflicts

0x20492d53…80f9

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0x482471adbb…39122f

← previous block·next block →recent activity