← previous blocknext block →recent activity

Analyzing

Block #98,837,963

27 transactions · 25 stateful · 2026-08-24 19:11:26 UTC

Parallelism

78/100

Blocked

32%

Avg conflicts / tx

0.41

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,837,963  ·  27 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

0xd984a5e4…5cfc

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x57330c5d…9973

0x34b655…2a6f

4 touches
1 conflict

0x5ddd9edb…6ce7

0x34b655…2a6f

4 touches
1 conflict

0x67a56c8b…f955

0x34b655…2a6f

4 touches
1 conflict

0x7304f0da…c7e9

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0x820c9de7…b517

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 0xd984a5e4e9…3a5cfc

← previous block·next block →recent activity