← previous blocknext block →recent activity

Analyzing

Block #98,777,501

15 transactions · 15 stateful · 2026-08-24 14:07:02 UTC

Parallelism

73/100

Blocked

47%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,777,501  ·  15 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

0x772b55e3…82f3

0x8964d7…10f8

4 touches
1 conflict

0x772b55e3…82ed

0x8964d7…10f8

4 touches
1 conflict

0x772b55e3…82f0

0x8964d7…10f8

4 touches
1 conflict

0x772b55e3…82f1

0x8964d7…10f8

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

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: 0x8964d7c9…5b10f8

1 conflict on slot 0x772b55e3f4…3282f3

← previous block·next block →recent activity