← previous blocknext block →recent activity

Analyzing

Block #98,216,287

18 transactions · 17 stateful · 2026-08-22 14:27:10 UTC

Parallelism

56/100

Blocked

47%

Avg conflicts / tx

1.67

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #98,216,287  ·  18 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

12 touches
15 conflicts

0x886db264…846e

0x34b655…2a6f

12 touches
15 conflicts

0x92385428…6941

0x34b655…2a6f

12 touches
15 conflicts

0xdd23c3a7…53e4

0x34b655…2a6f

8 touches
6 conflicts

0x5c95d183…6321

0x34b655…2a6f

6 touches
3 conflicts

0x0299d0eb…ce68

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0007

0x340143…768f

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity