← previous blocknext block →recent activity

Analyzing

Block #98,745,113

27 transactions · 23 stateful · 2026-08-24 11:23:57 UTC

Parallelism

85/100

Blocked

30%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,745,113  ·  27 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

0xb482658a…e4f5

0x34b655…2a6f

6 touches
3 conflicts

0x2b54cadb…4425

0xd18b7e…414b

6 touches
3 conflicts

0x002fed35…79fa

0x2a68ba…90c5

6 touches
3 conflicts

0xead15497…1dbe

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xf13710d4…c78b

0x40c49f…2af0

5 touches
3 conflicts

0x5b6af007…0f35

0x34b655…2a6f

4 touches
1 conflict

0x74e46435…fdcd

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 0xb482658a15…f3e4f5

← previous block·next block →recent activity