← previous blocknext block →recent activity

Analyzing

Block #97,187,209

17 transactions · 14 stateful · 2026-08-18 23:09:27 UTC

Parallelism

53/100

Blocked

64%

Avg conflicts / tx

1.76

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #97,187,209  ·  17 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x11b69a7e…334e

0x01bff4…1071

16 touches
28 conflicts

0xa1087a5c…66c4

0x754704…b603

16 touches
28 conflicts

0x07b86c51…cdae

0x2a68ba…90c5

8 touches
6 conflicts

0x5b868e17…7fa2

0x851145…3f07

8 touches
6 conflicts

0x002fed35…79fa

0x2a68ba…90c5

8 touches
6 conflicts

0x187a055c…4d6a

0x851145…3f07

8 touches
6 conflicts

0x3040553c…5e28

0x754704…b603

4 touches
1 conflict

0x3d9eb674…b3fb

0x754704…b603

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: 0x01bff417…bc1071

28 conflicts on slot 0x11b69a7ea1…83334e

← previous block·next block →recent activity