← previous blocknext block →recent activity

Analyzing

Block #93,921,118

23 transactions · 20 stateful · 2026-08-07 12:35:05 UTC

Parallelism

78/100

Blocked

40%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,921,118  ·  23 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

0x4b40449d…e1bd

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x0463db49…5d05

0x34b655…2a6f

6 touches
3 conflicts

0x22ced833…fe1e

0x34b655…2a6f

4 touches
1 conflict

0x4f1ad4b4…e00a

0x34b655…2a6f

4 touches
1 conflict

0x67a2142d…4daa

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 0x4b40449d1a…b8e1bd

← previous block·next block →recent activity