← previous blocknext block →recent activity

Analyzing

Block #100,142,212

16 transactions · 16 stateful · 2026-08-29 08:56:28 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,142,212  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xbee5cfda…5e91

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x18e86f02…fa98

0x34b655…2a6f

4 touches
1 conflict

0x35b0198e…3e0d

0x34b655…2a6f

4 touches
1 conflict

0x9210e826…1414

0x34b655…2a6f

4 touches
1 conflict

0x948836ff…59ab

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity