← previous blocknext block →recent activity

Analyzing

Block #98,064,012

16 transactions · 16 stateful · 2026-08-22 01:40:18 UTC

Parallelism

88/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #98,064,012  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x66a542a3…dbfe

0x851145…3f07

4 touches
1 conflict

0x00000000…0007

0x340143…768f

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0xa7f15927…3b38

0x851145…3f07

3 touches
1 conflict

0x62811193…186c

0x2b46c0…1669

2 touches
0 conflicts

0x62811193…186d

0x2b46c0…1669

2 touches
0 conflicts

0x7a12283f…b18a

0x2b46c0…1669

2 touches
0 conflicts

0x7a89325a…d7e0

0x2b46c0…1669

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: 0x851145ea…9f3f07

1 conflict on slot 0x66a542a3a0…8edbfe

← previous block·next block →recent activity