← previous blocknext block →recent activity

Analyzing

Block #101,657,808

20 transactions · 18 stateful · 2026-09-03 16:06:07 UTC

Parallelism

60/100

Blocked

61%

Avg conflicts / tx

1.7

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #101,657,808  ·  20 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

0xca841faa…486a

0x34b655…2a6f

16 touches
28 conflicts

0x00000000…0002

0xf5b5f7…6d70

4 touches
1 conflict

0x51af0e92…4020

0x34b655…2a6f

4 touches
1 conflict

0x775a8ad3…8307

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xab981df1…2941

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xc2abbe8a…78cf

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

28 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity