← previous blocknext block →recent activity

Analyzing

Block #97,731,314

18 transactions · 17 stateful · 2026-08-20 21:31:43 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

0.56

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #97,731,314  ·  18 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

0x37ed7ce3…537f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xd2274a53…9d6a

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x4de0b2a2…784f

0xc8689a…ee79

4 touches
1 conflict

0x7d3edcbd…ead6

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0x82dd2252…e1ce

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 0x37ed7ce3bf…b0537f

← previous block·next block →recent activity