← previous blocknext block →recent activity

Analyzing

Block #98,000,556

21 transactions · 21 stateful · 2026-08-21 20:20:44 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,000,556  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf79df061…e005

0xe52b14…7230

12 touches
15 conflicts

0x8ffa3328…ce11

0xe52b14…7230

8 touches
6 conflicts

0xf275b4ca…57b8

0xe52b14…7230

6 touches
3 conflicts

0x00000000…0007

0x340143…768f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x31ef4e0d…2944

0x34b655…2a6f

2 touches
0 conflicts

0x386d08f4…5a01

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: 0xe52b1424…bb7230

15 conflicts on slot 0xf79df061c7…91e005

← previous block·next block →recent activity