← previous blocknext block →recent activity

Analyzing

Block #99,481,916

22 transactions · 22 stateful · 2026-08-27 01:18:42 UTC

Parallelism

82/100

Blocked

36%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,481,916  ·  22 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

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0xd1df28f5…d093

0x34b655…2a6f

6 touches
3 conflicts

0x6c60fbcf…8744

0x34b655…2a6f

6 touches
3 conflicts

0x904e2bfb…1544

0x34b655…2a6f

6 touches
3 conflicts

0xfa09be5a…1e79

0x34b655…2a6f

4 touches
1 conflict

0x1867b653…e61b

0x34b655…2a6f

4 touches
1 conflict

0x18a8536c…4a40

0x34b655…2a6f

4 touches
1 conflict

0xb3a1165e…2b84

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

3 conflicts on slot 0xb3fb9fb561…7664db

← previous block·next block →recent activity