← previous blocknext block →recent activity

Analyzing

Block #98,014,958

28 transactions · 20 stateful · 2026-08-21 21:33:19 UTC

Parallelism

79/100

Blocked

45%

Avg conflicts / tx

0.79

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,014,958  ·  28 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

0x00000000…0002

0xbb3f3c…e046

12 touches
15 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x41be9e75…9773

0x34b655…2a6f

4 touches
1 conflict

0x4fc6ff4d…be39

0x34b655…2a6f

4 touches
1 conflict

0xca1ae27b…4f80

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

2 touches
0 conflicts

0x808bba43…159a

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: 0xbb3f3cb7…74e046

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity