← previous blocknext block →recent activity

Analyzing

Block #98,442,941

26 transactions · 23 stateful · 2026-08-23 09:27:29 UTC

Parallelism

85/100

Blocked

30%

Avg conflicts / tx

0.31

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,442,941  ·  26 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

0xeb5b61a2…b2bc

0x34b655…2a6f

6 touches
3 conflicts

0xc9c17729…ac91

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xf690d06e…5e46

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7db78f05…2895

0x34b655…2a6f

4 touches
1 conflict

0x42041fec…bd86

0x754704…b603

4 touches
1 conflict

0xac2a0273…721b

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 0xeb5b61a29c…4fb2bc

← previous block·next block →recent activity