← previous blocknext block →recent activity

Analyzing

Block #100,627,392

23 transactions · 19 stateful · 2026-08-31 01:41:29 UTC

Parallelism

87/100

Blocked

26%

Avg conflicts / tx

0.26

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,627,392  ·  23 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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…004c

0x80c745…7210

4 touches
1 conflict

0x87d39100…7270

0x851145…3f07

4 touches
1 conflict

0x474e5df9…821f

0x851145…3f07

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5f77d607…2c84

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

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: 0x80c74517…647210

1 conflict on slot 0x0000000000…00004c

← previous block·next block →recent activity