← previous blocknext block →recent activity

Analyzing

Block #98,012,914

21 transactions · 20 stateful · 2026-08-21 21:23:02 UTC

Parallelism

81/100

Blocked

30%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,012,914  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x112f66a5…17d2

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x064bb149…79fd

0x34b655…2a6f

4 touches
1 conflict

0x08ff4d66…96de

0x34b655…2a6f

4 touches
1 conflict

0x1b5a25fd…5b2f

0x34b655…2a6f

4 touches
1 conflict

0x1db5837f…1264

0x34b655…2a6f

4 touches
1 conflict

0x4755fafb…859b

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

3 conflicts on slot 0x112f66a5ea…1017d2

← previous block·next block →recent activity