← previous blocknext block →recent activity

Analyzing

Block #96,132,345

22 transactions · 18 stateful · 2026-08-15 06:30:26 UTC

Parallelism

45/100

Blocked

61%

Avg conflicts / tx

3

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #96,132,345  ·  22 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x00000000…0031

0x59df86…2780

24 touches
66 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x889d5e90…929a

0x2a68ba…90c5

2 touches
0 conflicts

0x213ee207…a151

0x2b46c0…1669

2 touches
0 conflicts

0x46279ae7…20dd

0x2b46c0…1669

2 touches
0 conflicts

0x53e50026…6d8c

0x2b46c0…1669

2 touches
0 conflicts

0x7f4a8466…f2cc

0x2b46c0…1669

2 touches
0 conflicts

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: 0x59df8637…6d2780

66 conflicts on slot 0x0000000000…000031

← previous block·next block →recent activity