← previous blocknext block →recent activity

Analyzing

Block #97,357,946

27 transactions · 22 stateful · 2026-08-19 13:36:07 UTC

Parallelism

74/100

Blocked

41%

Avg conflicts / tx

1.07

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #97,357,946  ·  27 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xa3f095f5…bd87

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x12f129f2…fe6b

0x2b46c0…1669

4 touches
1 conflict

0x260cc5c4…bef0

0x2b46c0…1669

4 touches
1 conflict

0x39977254…07b1

0x2b46c0…1669

4 touches
1 conflict

0x3a3e7727…36c5

0x2b46c0…1669

4 touches
1 conflict

0x5a409e7f…09b6

0x2b46c0…1669

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

15 conflicts on slot 0xa3f095f5ab…55bd87

← previous block·next block →recent activity